Between 10-16 October 2026, compromised third-party Shopify apps redirected shoppers to fake checkout pages that stole card details. Shopify's own platform wasn't breached - but your app stack might be the weak point.

Shopify's own platform and checkout were not compromised in this incident. What happened, between 10 and 16 October 2026, is that attackers compromised a small number of third-party Shopify apps and used the access they already had to inject code that redirected some shoppers to lookalike checkout pages, capturing card details before quietly sending the shopper on to the real checkout, so the order still completed and nothing looked obviously wrong. If you run any of the affected apps, this is worth a careful read, not a quick skim.
The apps involved all have one thing in common: they inject their own code directly onto storefront pages that shoppers interact with (product option pickers, wishlists, upsell pop-ups), which puts them in a genuinely sensitive position, right next to where customers enter payment details, even though none of them are payment apps themselves. Once compromised, the injected code intercepted the "Checkout" click and redirected the shopper to a fake external checkout page designed to capture their card details. The genuinely nasty part is what happened next: rather than leaving the shopper stranded on an obviously broken page, the attack forwarded them on to the real Shopify checkout afterwards, so the order completed normally. A shopper who got caught by this had no real-time signal that anything had gone wrong: the card details were simply gone before they ever reached the legitimate checkout.
Hulk Product Options, Selleasy and Swym Wishlist Plus are the three apps confirmed as affected at the time of writing. Treat this as the list as it stood during the incident window, and check current advisories if you're reading this later, since further apps could in principle have been identified afterwards. Shopify's response centred on getting the affected apps pulled from the App Store and shipping the new CLI/AI Toolkit security check rather than a platform-side fix, which is consistent with this being an app-layer compromise rather than anything touching Shopify's own infrastructure.
This is precisely the e-skimming threat that PCI DSS 4.0.1's client-side security requirements exist to catch: a trusted script, already approved and running on a checkout-adjacent page, gets compromised and starts doing something it shouldn't. That post is written with a Magento example in mind, but the underlying principle (inventory every script that touches your checkout flow, and monitor for unauthorised changes) applies just as directly to a Shopify app stack.
Do I need to tell my customers if I used one of the affected apps? That depends on your specific exposure and your jurisdiction's breach-notification requirements. This is a question worth putting to your legal counsel or data protection advisor rather than assuming either way, given how much depends on the specifics of your own store and customer base.
How do I audit which Shopify apps have checkout or script access? Review each installed app's requested permissions in your Shopify admin, paying particular attention to anything with storefront script injection or checkout-related scopes, not just apps that explicitly describe themselves as payment-related.
Is this covered by Shopify's own security guarantees, or is it on the merchant? Shopify's core platform and checkout were not compromised here: the exposure sat with the third-party apps and, by extension, the merchants running them. Vetting and monitoring your app stack is squarely a merchant responsibility, which is exactly why an app permissions audit is worth treating as routine rather than reactive.
If you'd like your current app stack reviewed for exactly this kind of exposure, Deploy can run that audit for you alongside the wider security work we do across both Magento and Shopify.
Sources: Roman Zipp's original writeup and follow-up with vendor statements, cSide's analysis of the HulkApps incident, LetsMetrix's incident timeline.
Last updated 16 October 2026.