Shopify app audit before Black Friday: 4 steps to stop fake checkouts
A Shopify app audit before Black Friday (November 27, 2026) comes down to four steps: inventory every app that runs on your storefront, assign an owner to each one, uninstall the apps nobody owns, and test checkout in a fresh private window through Cyber Monday (November 30). The reason: since October 2026, malicious code delivered through third-party app configurations has sent some shoppers to fake payment pages, while merchants' own checks often looked completely normal.

Why a Shopify app audit before Black Friday matters this year
The October 2026 attacks did not break into Shopify's checkout or merchants' themes. They came through apps. According to developer Roman Zipp, who first reported the activity on October 10, 2026, affected app extensions loaded their configuration from the app developer's servers each time a page opened. A custom JavaScript field in that configuration carried code that intercepted the Checkout click, sent the shopper to a look-alike domain to collect card details, and then passed them back to the real checkout. The order still completed, so nothing looked wrong in the admin.
Two details make this easy to miss. The script fired only once per browser session and marked itself as done. And according to HulkApps' statement, the redirect did not happen on every visit and was blocked by some browsers.

The developers of Hulk Product Options, Selleasy and Swym Wishlist Plus confirmed incidents. Other apps were pulled from the App Store during the same period, but not all of them have been confirmed as related. No source so far shows that Shopify's core checkout was compromised. For the full timeline, see our report on the Shopify Checkout Hijack campaign.
The timing raises the stakes. Shopify reported that its merchants sold $14.6 billion over Black Friday–Cyber Monday 2025, with sales peaking at $5.1 million per minute at 12:01 p.m. EST on Black Friday, and cross-border orders making up 16% of the total. The minute your traffic peaks is also the minute a hijacked checkout does the most damage.
Steps 1 - 2: Inventory storefront apps and assign an owner
Start with a list, not a new security tool. The more apps a store has added over past sales seasons, the more code runs in front of shoppers that nobody on the team remembers approving.
Step 1 - Inventory. Open Settings › Apps and sales channels to see every installed app. Then go to Online Store › Themes › Customize › App embeds to see which apps are actively loading code on your storefront. Flag three groups first:
Customer-facing apps: product options, wishlists, upsells, reviews, pop-ups, chat, search and filters.
Apps with fields that accept custom JavaScript or HTML. Treat text fields that accept HTML (button labels, translations, tooltips) as code fields too, because they can carry code.
Apps nobody remembers installing, or whose settings nobody has opened in months.
Step 2 - Assign an owner. For each app, ask one question: who on the team would notice if this app disappeared tomorrow? That person confirms the configuration, reads the developer's security notices and decides whether to keep or remove it. If an agency runs the store, write down whether the point of contact is the agency, the merchant or the app developer.
The register below is a framework proposed by IPSIP Vietnam, not data from a real customer. You can reuse it for Cyber Week, the holiday season and January sales.
Storefront app register (illustrative example)
App | Runs on storefront | Code/HTML fields | Owner | Decision | Config last confirmed |
Wishlist app | Yes (app embed on) | Yes | E-commerce lead | Keep, review weekly | Nov 20, 2026 |
Last season's promo pop-up | Yes | Yes | Unknown | Uninstall before Nov 25 | Not confirmed |
Product reviews app | Yes | No | Marketing | Keep | Nov 20, 2026 |
Invoicing app | No (admin only) | No | Finance | Keep | Nov 20, 2026 |
Upsell app in trial | Yes | Yes | Agency | Defer until after Cyber Monday | Not confirmed |
Step 3: Uninstall apps with no owner, then freeze changes
The rule is simple: if an app runs on your storefront and nobody owns it, uninstall it rather than just switching it off. If someone needs it after the sales season, they can request a reinstall with a clear reason.
Disabling an app embed is not the same as uninstalling. Turning off the embed only stops that block of code loading on your theme. The app keeps its access to store data and can be switched back on. Uninstalling is what revokes the app's access.
For apps you keep, open every code and HTML field. Someone on the team should recognize every snippet in there. If a snippet has no clear origin, ask the developer in writing before deleting it, so you keep a record if an investigation is needed later.
Check the theme after uninstalling. Some older apps inserted snippets directly into theme files and may leave code behind after removal. Ask a developer or your agency to check on a duplicate theme rather than editing the live one.
Lock down accounts. Change passwords and enforce two-factor authentication on Shopify and on the admin dashboard of every app you keep. Review staff accounts, collaborator access and any tools that still hold access to the store.
Once the audit is done, apply a change freeze through Cyber Monday. Don't install new apps or enable new features on existing ones. The only exception is a security patch, and every update should be followed by an immediate checkout test. This is a standard IT operations practice: make fewer changes at the moment the system carries the most load.
Step 4: Test checkout the right way through Cyber Monday
A checkout test is the only step in this process that can catch a redirect while it is happening. It has to be done correctly, because the script runs once per session and reacts only to the Checkout click.
Open a brand-new private or incognito window. Close any private windows you already had open.
Go to a product page and add the product to the cart.
Click the standard Checkout button, not Shop Pay or another express payment button.
Look at the address bar the moment the payment page loads. It should show your store's domain or your store's myshopify.com address.
Close the window and repeat twice more: once checking out from the slide-out cart drawer, and once on a phone.
Suggested cadence: test after every app or theme change, at least weekly until November 30, and daily from November 27 to 30, when traffic is highest. Stores run by an agency should keep a log of each test: time, tester, device and the domain they saw.
Since October 20, 2026, Shopify has shown a confirmation prompt when a storefront sends shoppers to an outside website. According to the changelog update of October 23, Shopify now blocks only sites already identified as malicious and asks for confirmation only on suspicious ones. Other outbound links go straight through. A freshly registered fake domain may not be on that list yet, so the prompt does not replace your own tests.
If you see an unfamiliar domain: don't enter any card details. Take a screenshot and note the time and URL. Contact the app developer in writing, open a case with Shopify Support and inform your payment provider. Treat it as a security incident until the cause is confirmed.
What the audit means for PCI DSS and GDPR
For merchants selling into the US, UK and EU, an app audit is also compliance evidence. This section is an editorial summary, not legal or QSA advice.
PCI DSS v4.0.1 and SAQ A. In January 2025, the PCI Security Standards Council revised SAQ A, the shortest self-assessment for merchants that fully outsource payment pages. It removed Requirements 6.4.3, 11.6.1 and 12.3.1 as line items. In their place, it added an eligibility criterion: the merchant must confirm that its site is not susceptible to attacks from scripts that could affect its e-commerce systems. The requirements themselves remain in the standard. The revised SAQ A applied from March 31, 2025.
If your acquirer asks you to validate on SAQ A, a dated app register and a checkout test log are practical evidence that you actually manage the scripts on your storefront. Confirm the exact evidence your acquirer or QSA expects.
GDPR. If shoppers in the EU or UK were redirected and entered personal data on a fake page, assess whether this counts as a personal data breach. Under Article 33, a controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to people's rights and freedoms. Breaches must be documented either way. In the US, notification rules vary by state, so involve legal counsel early.
What this audit doesn't cover, and when to bring in specialists
The four steps tell you whether your storefront is clean at the moment you check. They can't answer three questions:
Were shoppers redirected before? Today's test only reflects today. If your store used an affected app in October, ask the developer in writing, watch for customer reports of unexpected card charges and talk to your payment provider before peak traffic.
Is the rest of the store secure? This process doesn't cover theme code, Customer events pixels, private apps built by an agency or staff permissions.
Is the risk on your side? If you build Shopify apps, or run an agency with internal tools that write to storefronts, the weak point may be in your own infrastructure.
That last case is the background to IPSIP's Shopify incident response and pentest engagement for ShineCommerce – Smind Sections. Six stores using the Smind Sections app reported abnormal redirects. The investigation traced the entry point to an internal admin tool that lacked authentication and authorization controls, and found no personal data leak within the investigated scope. A follow-up Grey-box Web/API penetration test found one High-severity issue (Broken Access Control, CVSS 8.1), which was fixed and verified by retesting.
-----------
FAQ
Does a Shopify app audit before Black Friday need a developer?
Mostly not. A store owner or operator with admin access can do the inventory, assign owners, uninstall apps and test checkout. Bring in a developer or agency for two tasks: checking the theme for code left behind after uninstalling, and reviewing theme code, pixels or private apps if the store is heavily customized.
Our store doesn't use the three named apps. Do we still need to audit?
Yes. App developers reported different time windows and levels of impact, and several other apps were pulled from the App Store during the same period. More importantly, the attack works through any app that is allowed to load code on your storefront. The real question isn't whether you use app X, but how many sources of code you let run in front of your customers.
Conclusion
A Shopify app audit before Black Friday does more than another security plugin: it cuts the number of code sources running in front of shoppers and makes someone accountable for each one. Inventorying apps, assigning owners, removing what nobody owns and testing checkout correctly give you an early warning for the kind of attack seen in October. The app register you build now also carries over to the holiday season and January sales.
If your store runs many storefront apps, is managed by an agency, or your business builds apps for the Shopify ecosystem, IPSIP Vietnam can assess your storefront security and run web and API penetration testing before your next peak. For teams running multiple storefronts or backend integrations, SOC 24/7 monitoring adds continuous alert validation after remediation. Contact IPSIP Vietnam to discuss the right scope.
--------------
References
Shopify shops hit with ongoing Checkout Hijack attack (Roman Zipp, including HulkApps and Selleasy statements): https://romanzipp.com/blog/shopify-hit-with-phishing-attack
Shopify Narrows Its Leave-Store Warning to Risky Sites (Ecommerce Paradise, summary of Shopify changelog updates of October 20 and 23, 2026): https://ecommerceparadise.com/shopify-narrows-leave-store-warning/
Shopify Merchants Achieve Record-Breaking $14.6 Billion in Black Friday-Cyber Monday Sales (Shopify, December 2, 2025): https://www.shopify.com/investors/press-releases/shopify-merchants-achieve-record-breaking-146-billion-black
SAQ A Changed. E-commerce Payment Page Risk Did Not (Tevora): https://www.tevora.com/resource/saq-a-changed-e-commerce-payment-page-risk-did-not/
PCI DSS SAQ A updates, effective March 31, 2025 (Halock): https://www.halock.com/?p=36139
GDPR Article 33 – Notification of a personal data breach to the supervisory authority: https://gdpr-text.com/en/read/article-33/











