All guidesShopify maintenance

Shopify checkout hijack: test your store, check your apps, plan for the app deadlines

How to test your store after the October 2026 app attacks, what to ask each app vendor, and what Shopify's IP allowlist and token deadlines change from 12 November.

The short version

The Shopify checkout hijack of October 2026 was an attack through third-party apps, and we found no public evidence of a breach of Shopify's own checkout. Injected code sent some shoppers from the checkout button to a fake payment page. To check your store, open a fresh private window, add a product, click your real checkout button and read the address bar, then repeat on a phone. Separately, Shopify now requires IP allowlists on public apps: bulk operations fail after 12 November, non-compliant apps are delisted after 20 November, and Admin API calls fail from 1 April 2027.

Three separate events are being reported as one

The October 2026 reports mix an attack on a few apps, a wave of App Store delistings and a set of new Shopify security rules. Each one calls for a different response, so separate them before you change anything.

  • The attack. Code added through third-party apps waited for a shopper to click Checkout, then sent some of them to a fake payment page. Developer Roman Zipp's technical write-up describes that page collecting the form and then forwarding the shopper to the real checkout. We found no detailed Shopify account of the incident as of 6 November 2026. A spokesperson told iTnews on 17 October that "When an app falls short, we act," and that its actions can include delisting. No vendor statement we read gives a count of stores or shoppers.
  • The delistings. One vendor's tracker, using heyapps.dev's App Store archive, reports 563 apps delisted since 14 October, as of 27 October, and says 108 delisted apps have since returned. The same page says Shopify has not explained most removals and that a delisting is no verdict on an app. Digismoothie reports Atlee Clark of Shopify saying most were not removed for security reasons; we could not open the original post. Stores that already have a delisted app keep it, along with any script it adds, until they uninstall.
  • The new rules. Shopify's 5 November post sets dates for IP allowlists and expiring access tokens on public apps. These rules apply to every public app that calls the Admin API, whether or not it was involved in the attack.

Three vendors have published or given statements confirming unauthorized code. Times below are UTC, so add 5 hours 30 minutes for IST.

AppWindow the vendor givesWhat the vendor saysWhat it asks of merchants
Hulk Product OptionsFrom 10 October; we found no end timeAn exploit added unauthorized configuration to its theme extension, quoted in Zipp's postWe found no merchant steps from the vendor, so ask it directly
Selleasy13 October, 07:47 to 12:22 for redirects; script removed by 15:58An attacker reached a legacy internal support tool, per Logbase's report. Re-listed on 27 October after Shopify's reviewNo action needed inside the app
Swym Wishlist Plus14 October, configuration changed 10:06 to 11:56; fixes live at 16:32An unauthorized configuration change, per Swym's FAQ, which also says it paused the app for all merchants and is restoring access in phasesSearch theme files for checkout-guard and report shopper complaints. Its notice also asks merchants to consider telling shoppers who typed a card number directly into checkout between 10:06 and 16:32

Other apps have been named on trackers and in forums without confirmation from their makers. Treat a name on such a list as a reason to ask the vendor, and leave conclusions until you have an answer.

Test checkout with the real button, in a fresh session

A useful test takes a few minutes: a private window, a real product and your own checkout button. The script Zipp traced ran once per user and shop in a browser session, so a repeat test in the same window can pass while the code is still live.

  1. Open a new private window and go to your storefront.
  2. Open a product page and add the product to the cart.
  3. Click your normal Checkout button. Skip express wallet buttons for this test, because the injected code was attached to the checkout click.
  4. Read the address bar before you type anything.
  5. Close every private window, then repeat from the cart page and from a collection page if your theme allows adding to cart there. Swym names product, collection and cart pages as the places its script loaded.
  6. Repeat once on a phone.

Then read the result:

  • Your own domain or a Shopify address. A pass for that session.
  • Your third-party checkout. Razorpay Magic Checkout, Shiprocket Checkout and GoKwik change what shoppers see after the click, so a store using one cannot apply the Shopify-only rule. Write down what normal looks like on your store before you test, including any domain the provider uses.
  • Any other domain. Stop, enter nothing, take a screenshot that shows the address bar, note the time and go to the section below on fake checkouts.

Three limits of this test

  • A cart permalink cannot find this. The permalink test in our checkout troubleshooting guide goes past your theme's cart button, which is exactly where this code was listening.
  • A clean theme proves little. Zipp found about 22.7 KB of JavaScript arriving from the vendor's server at runtime, so it sat in no theme file. Search your theme as well, under Online Store, then Themes, then Edit code, and keep in mind that an empty result only covers the theme.
  • A pass covers that moment only. Settings held on a vendor's server can change without a theme edit, and HulkApps says not every visit was redirected and some browsers blocked the redirect. Run several fresh sessions, then repeat the test after any app update and each morning during your peak.

For a developer, Zipp lists two further signs: session storage keys beginning with __ctf, and these domains, written here with brackets so they stay unclickable: biliing[.]top, checkout-confirm[.]top, order-confirm[.]top, account-confirm[.]top and billing-confirm[.]top. Swym's FAQ adds checkout-guard[.]top and checkout-secure[.]top. A merchant's comment on Zipp's post names cartassure[.]top, which we could not confirm elsewhere. Other domains may exist, so a clean search is one signal among several.

Shopify's redirect protection helps but should not replace this test. Since its 23 October update it blocks only sites Shopify has identified as malicious and asks for confirmation on suspicious ones. Zipp's post reports that some of these domains were missing from public blocklists at the time of writing.

Review the apps that can put code on your storefront

The apps that matter most for this attack are those that run code on your storefront, and above all those with a field for custom JavaScript or HTML. Qikify's notice in Zipp's statement roundup describes a separate July incident in which malicious code was placed in two HTML fields in app settings.

  1. List your apps. Go to Settings, then Apps. Shopify's app management page says each app's about page shows Activity and permissions, including Unused access for permissions untouched in 30 days.
  2. List your app embeds. Go to Online Store, then Edit theme, then the App embeds icon. Every active embed is a script route onto your storefront, and the toggle is reversible.
  3. Open each storefront app's dashboard. Look for custom JavaScript, custom HTML or custom CSS fields. Clear what your team did not add, after keeping a copy.
  4. Remove what you no longer use. Our app audit guide covers how to decide, and how to find code an uninstalled app left behind.

Change passwords and turn on two-step authentication as routine hygiene, and review who has access using our guide to developer access. Keep expectations realistic: Swym says the activity used the app's access and did not use staff accounts, so a new password would not have stopped that case.

The first app deadline falls on 12 November

Bulk operations from public apps without an IP allowlist fail after 12 November 2026, more than four months before the April date. Shopify says existing installs keep working until 1 April 2027, and its own table makes bulk operations the exception.

Date (11:59 PM ET where given)RuleWhat happensWhat you may notice
12 November 2026IP allowlistBulk queries and mutations from public apps without one are blockedLarge imports, exports or syncs from that app stop
20 November 2026IP allowlistApp is delisted, blocked from new installs and flagged in Settings, then AppsA flag on the app. Stores that have it keep using it
1 January 2027Expiring offline tokensApp is delisted, blocked from new installs and flaggedSame as above
15 January 2027BothMerchants using the app see a warning in the adminA warning about possible service interruption
1 April 2027BothAdmin API requests fail with a 403The app stops reading or writing store data

In India, 11:59 PM ET in November is 10:29 AM IST the following morning. Shopify's post gives 11 November for bulk operations in its summary and 12 November in its body and table, and its separate changelog entry says 12 November. Plan for the earlier date. That same entry lets developers request an extension, so one app's real date may differ from this table.

Shopify's bulk operations docs describe them as a way to retrieve large volumes of data. Our reading is that catalogue feeds, ERP and inventory connectors, search indexers and reporting tools are the ones to ask about first. The token dates come from Shopify's offline token entry, which says existing installs can keep making affected requests until 1 April.

A flag or a delisting calls for a dated answer from the developer

When an app is flagged or delisted, ask its developer for a date before you decide anything. Removing it the same day can cost you more than the flag does, especially this close to a sale.

Shopify says merchants can now see an app's expiring token and IP allowlist status in Settings, then Apps. Read it with some care. Developers in the community thread report tokens showing as missing after they migrated, and Shopify had not answered that point in the thread when we read it.

A clean status has limits too. Shopify's allowlist documentation says it checks GraphQL and REST Admin API requests. Selleasy's attacker came through an internal support tool, so a clean status tells you about stolen tokens and says little about a vendor's own tools.

If you decide to remove an app, follow this order:

  1. Turn off its embed first. It takes effect at once and you can reverse it. Swym's FAQ gives this same step for its paused app.
  2. Export its data. Shopify's uninstall page warns that some apps store data you cannot recover, and that settings may not return if you reinstall.
  3. Treat an uninstall as possibly final. An app blocked from new installs may refuse you a reinstall. Shopify does not spell this case out, so ask the developer, and avoid uninstalling and reinstalling as a troubleshooting step this month.
  4. Clean up after it. The same page says some apps add theme code that uninstalling does not automatically remove, and that charges billed outside Shopify continue until you cancel them through the app or its developer.

Custom apps are exempt, with two things to check

Shopify's IP allowlist and offline token deadlines exclude custom apps and apps created by merchants. If a developer built a private integration for your store alone, these dates do not apply to it.

Shopify still highly recommends an allowlist for custom apps, and your developer can set one in the Dev Dashboard for apps managed there. Two checks come first, both from the allowlist documentation:

  • Automations and headless storefronts. Tokens used by the Shopify Flow Send HTTP request action are rejected, and so are Admin API requests from a storefront on Oxygen, because Shopify cannot confirm the source address.
  • Where the integration runs. A rejected request returns a 403, so every server that uses the token has to be listed. Up to 100 IP addresses or ranges are allowed. Hosting without fixed addresses can use up to 10 ASNs, but Shopify warns that those networks are shared with other customers and advises individual addresses where possible.

If your developer cannot test the change properly before your peak, schedule it for after the peak. A failed order sync during Black Friday is a worse outcome than a recommended setting arriving in December.

Send every storefront app the same five requests

A written answer from each vendor gives you a record and exposes the ones that have not done the work. Send this to every app that runs on your storefront or moves your order and stock data.

  1. State the date your IP allowlist was or will be switched on, the date you moved to expiring offline tokens, and any extension Shopify has granted you.
  2. Confirm whether your app runs bulk operations on my store, and what stops if they fail after 12 November.
  3. List any custom code fields your app can run on my storefront, and who on your team or in your support tools can edit them.
  4. Confirm whether my store was affected by any unauthorized change since July 2026, with dates, times and what has been removed.
  5. Name a security contact and tell me how you will notify me of an incident.

Shopify's 20 October post to developers says they are responsible for fixing problems and notifying affected merchants, so these are reasonable things to ask. If a vendor has not replied by your code freeze, plan as if it has not done the work. Keep every response.

If a shopper reached a fake checkout, act the same day

Treat any credible report as an incident and start the same day, because the people at risk are your customers. Your order data will not clear you: the fake page forwarded shoppers to the real checkout, so an affected order can look normal in your admin.

  1. Keep the evidence. Save the full address, time, device, the page the shopper started from and any screenshots.
  2. Stop the route. Turn off the suspect app's embed, then repeat the test. Check theme file history if you found edits you do not recognise, since Swym notes Shopify keeps earlier versions. If the redirect continues, consider password protection until you find the source: iTnews reports Shopify support telling one affected merchant to keep it on during a review.
  3. Tell the vendor and Shopify Support. Ask the vendor in writing what ran, when, and on which pages. Keep the reply.
  4. Work out who was exposed. Pull orders and abandoned checkouts started in the window. Swym's notice, in Zipp's roundup, points to shoppers who typed a card number directly into checkout, and says wallets such as Shop Pay, PayPal and Google Pay were not affected the same way. Where your vendor gives no such split, include everyone who could have reached the button.
  5. Tell your payment provider and your customers. Shoppers should know what to look out for and should contact their bank about anything they typed on the fake page. State what you know and what you are still checking.

The reporting rules to check

Get legal advice the same day, because the clocks are short and this guide cannot tell you whether your case meets them.

  • India, now. CERT-In's directions require body corporates to report listed incidents within 6 hours of noticing them or being told of them. One legal summary lists phishing, data breaches and unauthorised changes such as inserted malicious code among them.
  • India, from about May 2027. Rule 7 of the DPDP Rules requires notice to affected people and the Board without delay, with a detailed report within 72 hours. Rule 1 starts it 18 months after publication, and the Rules were notified in November 2025.
  • EU customers. GDPR Article 33 sets 72 hours to notify the supervisory authority, unless the breach is unlikely to create a risk to people.

Finish this before your Black Friday code freeze

Black Friday falls on 27 November, one week after the delisting date, so any app replacement has to happen in the next two weeks. Here is the order we would use:

  • Today. Run the checkout test on desktop and phone. Send the five requests. List your embeds and custom code fields.
  • By 11 November. Hear back from any app that handles large catalogue, stock or order syncs, and agree a manual fallback for any that has no date.
  • By 20 November. Decide what to keep, replace or switch off. Finish any replacement before your freeze, and make sure the new app is still listed.
  • Peak week. Test checkout each morning. Change nothing that is not an emergency, following our BFCM readiness plan.
  • January 2027. Review Settings, then Apps again ahead of the 15 January warnings, and replace anything without a date before 1 April.

We look after stores on retainer through our Shopify maintenance service, and our average reply on working days is 11 minutes. If you want a second opinion on your app list before the peak, you can reach us through our contact page.

Questions

Was Shopify hacked in October 2026?

The public record points to third-party apps. HulkApps, Logbase and Swym each confirmed unauthorized changes that loaded code on some storefronts and redirected shoppers from the checkout button. We found no public evidence of a breach of Shopify's own checkout and no detailed Shopify account of the incident as of 6 November 2026, beyond a spokesperson's comment to iTnews, so treat this as the position known so far.

How do I check if my Shopify store has the checkout hijack?

Open a new private window, add a product to the cart, click your normal Checkout button and read the address bar before typing anything. Repeat in fresh windows from the cart page and on a phone, because the script Roman Zipp traced ran once per session. Your own domain, a Shopify address or your known third-party checkout is a pass for that session. Then review app embeds and custom code fields in your apps.

Does a delisted Shopify app stop working?

Usually not straight away. Delisting removes the app from the App Store and blocks new installs, while stores that already have it generally keep using it. Under the new security rules, bulk operations fail first, after 12 November 2026, and Admin API requests fail from 1 April 2027 for apps that have not complied. A delisting alone does not prove an app was compromised, so ask the developer why it happened.

Do merchants need to do anything about Shopify's IP allowlist requirement?

You do not set it yourself on public apps; each app's developer turns it on in the Dev Dashboard. Your job is to ask each vendor for the date, starting with apps that run large syncs, because those can fail after 12 November. You can see each app's status in Settings, then Apps, and apps without an allowlist are flagged after 20 November.

Do Shopify's IP allowlist and expiring token rules apply to custom apps?

No. Shopify's changelog excludes custom apps and apps created by merchants from both deadlines, although it highly recommends an allowlist for custom apps. If you add one, check first that nothing uses the token from Shopify Flow's Send HTTP request action or an Oxygen storefront, since Shopify rejects those requests. Every server using the token also has to be listed, or its calls return a 403.

Is uninstalling a compromised Shopify app enough?

Often not. Shopify's help page says some apps add theme code that uninstalling does not automatically remove, so search your theme files as well. Turn off the app's embed first, since that is immediate and reversible, and export any data you need. Charges billed outside Shopify also continue until you cancel them. Then run the checkout test again in a fresh private window to confirm the result.

What should I tell customers who may have reached a fake checkout?

Tell them what happened, when, and what you are still checking, and ask them to contact their bank about anything they typed on the fake page. Include a named contact at your company. Pull everyone who started checkout during the vendor's stated window, since affected orders can look normal in your admin. Take legal advice the same day, because reporting rules such as CERT-In's 6-hour direction in India may apply.

Get started

Talk to us about your store.

Average reply 11 min

Book a call

30 minutes with Suvam. Leave knowing what to fix, build or leave alone.

Book a call
Mon to Sat, 9 to 23 IST

Email us

A brief, a bug or a question. All welcome.

suvam@knox.team