The 2026 attacks ran on storefront pages, so start with the apps that add code to the pages shoppers see. In the Qikify incident, the redirect fired when shoppers clicked the Checkout button in a cart drawer, or the Add to Cart and Checkout buttons in a menu app.
Shopify's help article on extending your theme with apps names two ways apps appear in your theme:
- App blocks, which "let you add app functionality exactly where you want to use it in your theme."
- App embeds, which are "app-provided elements that float or display as an overlay in your theme, or add code to your online store without being visible to your customers."
To see your app embeds, go to Online Store, click Edit theme, and select the App embeds icon in the sidebar. Each embed has a toggle and its own settings. Note the apps that act on your cart, product options, or Checkout button, and run the permission checks on those first.
Tracking pixels work differently. Shopify's developer docs on web pixels say app pixels load "in a strict sandbox environment using web workers." Features "that rely on scraping the DOM for information or attempting to write to the DOM" don't work there. That means an app pixel can't read or change the page the shopper sees. Custom pixels, the ones you add yourself, load in a lax sandbox, and Shopify says they "cannot access the top frame."
You can also test your checkout the way a shopper would. cside's advice after the HulkApps case:
- Open a new private browser window, add a product, click the Checkout button, and watch the address bar.
- Close the window and repeat, because the 2026 script fired only once per session.
- Test from the cart drawer and on a phone too.
cside says "your checkout should stay on your own domain or your myshopify.com address."
These checks show what an app puts on your storefront. They can't show what a developer can change on its own servers, which is where the 2026 payloads were stored. Use them to decide which apps to watch and question first.