---
title: "Shopify Security Guide 2026: Apps and Tokens"
description: "Shopify security in 2026 for the store, its apps and tokens: IP allowlists, bulk operations, the Dev Dashboard move, and checkout phishing."
url: https://nodusworks.com/en/blog/shopify-security-guide-2026
markdown: https://nodusworks.com/en/blog/shopify-security-guide-2026.md
language: en
alternates:
  tr: https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026.md
  de: https://nodusworks.com/de/blog/shopify-sicherheitsleitfaden-2026.md
last_updated: 2026-11-21T22:36:00.000Z
type: article
published: 2026-11-22
author: "Efe Gündüz"
tags: ["Shopify"]
publisher: "Nodus Works"
---

# Shopify Security Developments and Hardening Guide 2026

> Shopify security in 2026 for the store, its apps and tokens: IP allowlists, bulk operations, the Dev Dashboard move, and checkout phishing.

![Blue and purple gradient cover, Nodus Works logo at the top left, white title Shopify Security Developments and Hardening Guide 2026](https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026/kapak-en.webp)

The common point of the three security incidents that became public in October and November 2026 was not the store password. It was an app connected to the store, or the access token that app held. The storefront can be open and checkout can still run on Shopify, while a customer's name, email and address have already left through an app.

In the same weeks Shopify tightened where that key can be used. Bulk operations no longer run until someone turns them on, an IP allowlist is now required for public apps, and older custom apps created in the admin are moving to the Dev Dashboard. Nodus Works, as a Shopify partner, received the App Security Update email sent to partners. The calendar below sets the jobs in that email next to the dates on shopify.dev.

## Who should read which part?

If you own the store, spend your time in three places. The five-minute check, the three autumn incidents, and the questions for your agency are things you can look at in the admin today. Spotting checkout phishing is yours too: you read the address bar, and the customer writes to you.

If you build at an agency, or on the store's own team, slow down on the app security update, the token hunt, and the 12 steps. The IP allowlist, the bulk operations switch, client secret rotation and the pre-release security scan live on your screens. The store owner may never see those screens. Your answer is what their question is waiting for.

Both of you can read the whole piece. The split is only about where to linger.

## What do these terms mean?

The docs keep the English names, and the admin prints them the same way. The table says what each one does for a store before the sentences need it.

| Term                  | What it does                                                                                                                                                                                         |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Token                 | The key an app sends with every API request. Its scopes limit what that request can read or write. Offline and online access tokens start with `shpat_`. Delegate access tokens start with `shppa_`. |
| Scope                 | The permission on a token. `read_customers` is enough to read a customer record. `read_orders` is enough to read an order. Card data can sit outside both.                                           |
| Custom app            | An app installed for one store or one organisation, and not published on the App Store. Older ones created under Develop apps are listed as legacy custom apps.                                      |
| Collaborator          | Partner access given without opening a staff account. Agencies usually come in this way.                                                                                                             |
| IP allowlist          | The list of addresses from which a token may call the Admin API. With enforcement on, a request from outside the list returns 403.                                                                   |
| Bulk operations       | A bulk query that reads many records at once, or a bulk mutation that writes them, through the GraphQL Admin API. The two are enabled separately.                                                    |
| Dev Dashboard         | The developer screen that holds an app's credentials, logs and IP allowlist.                                                                                                                         |
| Client transfer store | A store a partner builds for a client. It stays in the partner organisation until the client accepts the transfer.                                                                                   |
| Phishing              | Leading a customer onto a copy of a familiar page so they type a card or an account detail.                                                                                                          |

## Is my Shopify store safe?

Short answer: what was exposed in these incidents was not Shopify's own infrastructure. It was an analytics app's internal systems, a wishlist app's configuration, and the Admin API token of a store's own custom app in Japan. A store that opens without trouble does not show that customer data is safe. The store is as secure as its installed apps, its staff accounts and its tokens.

For a five-minute self-check, look at these six questions in the admin:

- In Settings, then Apps and sales channels, is there an app whose name you do not recognise?
- On the same list, is there a sales channel or online channel you no longer sell on?
- In Settings, then Users and permissions, is someone who has left the company still a staff member?
- Is there a collaborator account you do not recognise, and is the collaborator request code turned off?
- Has the Admin API token of a custom app you built yourself stayed the same for a long time?
- Have you recently told customers not to click a surprise shipping or refund message?

![The Apps and sales channels list in the Shopify admin, with an unused app row flagged](https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026/uygulama-listesi.webp)

If you cannot answer even one of these cleanly, start with the 12 steps below. Whether the token is still sitting in a theme file, a repository or an old handoff note is a separate checklist further down.

**Tip.** Start the first pass with apps. The shared lesson of this autumn was that a tool connected to the store can be the attacker's front door.

## What affected Shopify stores in autumn 2026?

In all three incidents, the path to customer and order data was an app the store trusted, or the token of the store's own custom app.

| Incident           | Date                                                                            | What happened                                                                                                                                                                                                                          | Lesson for the store                                                                                                     |
| ------------------ | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Triple Whale       | Detected 31 October 2026, contained 1 November 2026, statement 20 November 2026 | The analytics app said it had found unauthorised access to some of its internal systems. Affected parties were notified.                                                                                                               | If no notice arrived, no action is required on the Triple Whale account. Data types and store counts were not published. |
| Swym Wishlist Plus | Script 14 October 2026, FAQ 20 October 2026                                     | An unauthorised change in the configuration loaded a script, on a limited number of storefronts, that tried to redirect on a checkout click. The app was stopped on every store, Shopify access was revoked, credentials were rotated. | Check the theme files and the app embeds. The detail is on Swym's own FAQ.                                               |
| IMADEYA            | Statement 15 October 2026                                                       | The Admin API token of a Japanese store's own custom app reached a third party. Order and customer data was read from foreign IP addresses. Card data did not leak.                                                                    | A custom app token is a key separate from the staff password.                                                            |
| Shopify token docs | Current text read on 22 November 2026                                           | Uninstalling an app ends all of that app's tokens on this store. Revoking the client secret invalidates tokens minted with that secret. The next request returns 401.                                                                  | Incident order: contain, revoke credentials, keep the logs, write to <security@shopify.com>.                             |

### What did Triple Whale state?

On 20 November 2026 Triple Whale wrote on X that unauthorised access to some of its internal systems was detected on 31 October 2026. The incident was contained on 1 November 2026. The review was completed with third-party cybersecurity specialists. On that review, affected parties were notified. The company also said it had taken further steps to strengthen the security of its systems.

The sentence that matters for a store owner is the statement's own English: "If you have not received a notification from us, there is no action required on your Triple Whale account." If no notice arrived, there is nothing you need to do on your Triple Whale account. The statement does not name the way in, the kinds of data taken, or the number of stores affected.

In the notice Sneak Energy sent its own customers, it said name, email, phone, address and total spend were exposed, and that payment details and passwords were not in that set. That list is not Triple Whale's public statement. It is the text that store wrote to its customers. It does not follow that every store using Triple Whale lost the same fields. If the notice did not reach you, do not copy Sneak Energy's list onto your own store. Search your inbox for the company name. Do not click a notice whose link arrives inside a surprise message.

A post on a dark-web forum on 11 and 12 November 2026 claimed that Triple Whale's internal database held 91,310 Shopify tokens belonging to 20,510 stores, and that most of those tokens had been rotated. Triple Whale has not confirmed the numbers. Shopify has not confirmed them either. It is an unverified claim. Look at whether a notice reached you. Do not act on the forum's count.

**Warning.** 91,310 tokens and 20,510 stores are not a confirmed balance sheet. The official statement has no entry path, no data types and no store count.

### What happened at Swym Wishlist Plus?

According to Swym's incident FAQ of 20 October 2026, an unauthorised change was made to the Wishlist Plus configuration on 14 October 2026, between 10:06 and 11:56 UTC. The change loaded a script on a limited number of storefronts using the app. The script does not run on its own when the page opens. It fires when the shopper clicks checkout, and it tries to send them away from the store. Swym writes that it saw no finding that the script read form fields on the real storefront or on Shopify's checkout page.

Swym did not stop the app only on affected stores. It stopped it on every store at once. It revoked Shopify access for Wishlist Plus and for its other apps. It rotated credentials. The company says it saw no evidence that store data or customer personal information was taken from inside the app. If a redirected shopper typed their details by hand on an outside site, that entry carries a separate risk. Swym says that too.

Swym says it reached affected stores directly. If you want to check yourself, search the theme files for `checkout-guard.top` and for edits the Swym app made that you do not recognise. On the same page Swym also shares `account-confirm.top`, `billing-confirm.top` and `checkout-secure.top` as addresses it has seen in similar attacks across the Shopify ecosystem. Do not visit them. Search for the names in the theme and in the browser's address bar.

### What was stated about IMADEYA?

In the IMADEYA incident announced on 15 October 2026, the Admin API access token of a Japanese store's own custom app reached a third party. The token was used from foreign IP addresses to read order and customer data. What was read includes name, email, order number and amount. Card data did not leak. This is not a hack of an app installed from the App Store. It is the key of the store's own custom app leaving the building.

A custom app is still an app. Its token may be pasted into a theme file, an email or an old agency note. The [custom app development guide](https://nodusworks.com/en/blog/shopify-custom-app-development-api-tokenization-and-integration-guide) explains the token types in detail. The question here is who still holds that key.

### What do Shopify's docs say about tokens?

Read on 22 November 2026, Shopify's access token document states two rules plainly. When the merchant uninstalls the app, access ends for every token that app holds on this store. When the app's client secret is revoked, access ends for tokens obtained with that secret, and later requests return 401. A non-expiring offline token stays valid until the app is uninstalled or the client secret is revoked. The document also says that offline and online access tokens begin with `shpat_`, and delegate access tokens begin with `shppa_`. Searching a theme, a repository and a handoff note for those two prefixes is a shorter path than scanning for a leaked key by eye. A client secret does not carry those prefixes. Search for the secret string that sits next to a client ID as well.

Shopify's incident response document sets the order for the moment you suspect something: contain the incident, revoke exposed credentials, tokens and sessions, keep the logs instead of deleting them, and write to <security@shopify.com>. Then identify the affected stores and data, close the root cause, and meet your legal notification duties. The document is written for app developers. On the store side, its match is the incident plan in step 12 below. If personal data was exposed in Turkey, notice and request handling are a separate job. [KVKK integration](https://nodusworks.com/en/blog/shopify-kvkk-integration) covers that process.

## What does Shopify's app security update change?

The App Security Update that reached Nodus Works asked partners for four jobs. Turn on an IP allowlist on every app. Enable bulk operations only on the app that needs them. After a custom app is migrated, help the merchant with a tighter authentication setup and an allowlist. Run a security scan before every release. Alongside that: rotate tokens and client secrets that live in code, a repository or a handoff document, use two-step verification on every account, and remove access that is no longer needed. For the detail, the email points to the first 35 minutes of the [H2 2026 Partner Town Hall](https://www.shopify.com/webinar/partnertownhall-h2-2026) recording. The recording covers what changed for partners in data protection and app security.

One sentence in the email says an unused bulk operation turns off after 30 days. The [6 November 2026 changelog](https://shopify.dev/changelog/posts/partner-apps-must-enable-bulk-operations-before-use) and the bulk operations document both write the period as the last 31 days. The number to keep is 31. The email's shorter line, that an organisation cannot open a new app unless every existing app has an allowlist, is also wider than the document. The block, on the dates below, is installation onto stores outside the organisation.

### What is a bulk operation, and why does it start off?

A bulk operation reads or writes orders, products or customers through a job queue instead of one request at a time. Catalogue sync, an order archive and an inventory correction usually travel this way. If the same key is in someone else's hands, they can pull a much wider extract than a single request allows. Shopify therefore refuses `bulkOperationRunQuery` and `bulkOperationRunMutation` on an app that has not had that type enabled. Query and mutation are separate switches. Turning one on does not turn the other on.

Since 6 November 2026 this rule covers public apps a partner builds, and custom apps a partner builds. Apps that were already running bulk operations were left enabled by Shopify. You check that under Apps, the app, then API access requests in the Partner Dashboard. If a type has not started once in the last 31 days, access to that type drops and has to be enabled again. A sync that runs every night will never notice. A price file that runs once a quarter, or an order export that runs once a year for the accountant, fails on the day you need it, with access denied.

The 19 November 2026 update brought merchant custom apps, created in the Dev Dashboard or in the store admin, through the same door. Those apps enable bulk queries and bulk mutations from Access requests in the app's Dev Dashboard settings. The document writes the 31-day rule for apps managed in the Dev Dashboard as well. Leaving both off on an app that does not need them makes it harder for a leaked token to pull the whole customer table in the first hour.

### How does an IP allowlist limit a leaked token?

An allowlist says which source may use the token to call the GraphQL and REST Admin APIs. With enforcement on, Shopify looks at the source address of every request. An address on the list, or a network (ASN) on the list, passes. Anything else, and any request whose source Shopify cannot confirm, returns 403. A stolen token cannot call the Admin API from anywhere but the places you allowed. If the app never makes these calls with its own token, blocking every address also meets the allowlist requirement.

![A request from an allowed server passes, and a request from an unknown network is blocked](https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026/ip-izin-listesi.webp)

If you have a fixed egress address, enter the IPs one by one. That is the narrowest list. On serverless platforms the address changes. Then enter the host's ASN and the countries the app runs in. An ASN also lets in every other customer on that network. Shopify's own caution is this: use an ASN only for calls whose addresses you cannot write down, and limit it by country. Addresses and ASNs can sit together on one list. You can enter up to 250 addresses or ranges, 10 ASNs and 10 countries.

On public apps the list is now required. On 12 November 2026, bulk queries and bulk mutations stopped for public apps that had no list. As of 20 November 2026 at 11:59 p.m. ET, a public app without a list was delisted from the App Store, blocked from new installs, and flagged to the merchant under Settings, then Apps. The existing install keeps working. Shopify relists the app once the list is added. On 15 January 2027 the merchant sees a warning in the admin.

A custom app you install on a store outside your organisation needs a list too. Since 20 November 2026 a new install is made with an app that has one. On 1 January 2027 the rule widens: if even one of the apps you have already installed outside the organisation has no list, you cannot install any of your apps on stores outside the organisation after that date. On an app that lives only on stores inside your own organisation, a list is recommended and not required. Apps a merchant creates in the Dev Dashboard or in the admin sit outside this install rule. On those, the list is a control that becomes available once the move is done.

The Flow "Send HTTP request" action, and an Admin API call from a storefront hosted on Oxygen, cannot be matched to an allowlist, because Shopify cannot confirm the source address. Dev preview on a dev store, an embedded app page, an admin UI extension and a POS UI extension are not rejected because of the list. Before you turn the list on, run the test against the last 30 days of traffic. If your own server would be blocked, do not turn enforcement on.

### What happens when an old custom app moves to the Dev Dashboard?

Custom apps opened in the admin under Settings, Apps and sales channels, Develop apps are moving to the Dev Dashboard, according to Shopify's 17 November 2026 post. The move is not finished. The document still describes an app that has not moved yet. A moved app keeps its installation, its scopes and its existing Admin API token. The move does not replace the token on its own, and it does not turn the IP allowlist on. Once the app has moved, API logs, webhook logs and the IP restriction sit on the same screen.

An app that has not moved yet stays in the store admin. Its client secret cannot be rotated from the Dev Dashboard. The IP allowlist is a control on that screen, so it cannot be used until the move. The token is still on the app's card in the store admin, and it can be revealed once. The partner note that reached Nodus Works says merchant custom apps on client transfer stores that have not yet been transferred are still in this group for now. On those stores, do not write the token into theme code, a repository or a handoff document. Until the transfer is accepted, the key belongs in a password manager, not in a file.

When the move is done, do the next part with the merchant. Confirm the app appears with the installation and scopes you expect. If you know the server addresses, turn the allowlist on and watch the logs for a while to see that legitimate traffic still arrives. Because the old token is still valid, uninstall the app nobody uses, or rotate the token of the one you still use. On an admin-created app, a new Admin API token comes from uninstalling and reinstalling in the admin. Requests stop until the new token is in the code. Deleting the app in the Dev Dashboard is permanent, and you cannot open a new one of the same kind.

Every app created on or after 1 December 2026, including a custom app and an app the merchant creates, starts with an expiring offline token. The lifetime is one hour. Custom apps created before that date can keep their existing offline token. If you are opening a new one, a non-expiring key is no longer something you can wait for.

### Which dates are on the 2026 and 2027 calendar?

Five dates are the skeleton of the question a store owner asks an agency. For public apps, expiring tokens became required for new apps on 1 April 2026. 20 November 2026 is the hard edge of the allowlist. 1 December 2026 brings new custom apps onto expiring tokens as well. 1 January 2027 binds older public apps and installs outside the organisation. On 1 April 2027 an Admin API request from a public app that still presents a non-expiring token is rejected.

![Timeline marking 1 April 2026, 20 November 2026, 1 December 2026, 1 January 2027 and 1 April 2027](https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026/takvim.webp)

| Date             | What changes                                                                                                                                                                                                                                                                                                                |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 April 2026     | Public apps created on or after this date use expiring offline tokens. The lifetime is one hour.                                                                                                                                                                                                                            |
| 20 November 2026 | A public app with no allowlist is delisted, cannot take new installs, and is flagged under Settings, then Apps. The existing install keeps working. A new custom app install on a store outside the organisation also cannot be made without a list.                                                                        |
| 1 December 2026  | Custom apps and merchant-created apps created on or after this date start with expiring offline tokens. Earlier ones can keep their current token. If a public app that runs code on the storefront does not declare its network access, deploys and App Store submissions are rejected. The current version keeps working. |
| 1 January 2027   | A public app that still uses a non-expiring offline token is delisted, blocked from new installs, and flagged to the merchant. The existing install can keep making requests until April. If even one app already installed outside the organisation has no allowlist, no new install can be made outside it.               |
| 1 April 2027     | A GraphQL or REST Admin API request from a public app that presents a non-expiring offline token is rejected. The merchant loses access to that app until it authenticates again.                                                                                                                                           |

On 15 January 2027 a merchant using a public app that has no allowlist, or that still uses a non-expiring token, sees a warning in the admin. On 1 December 2026 the same missing declaration also rejects deploys of a custom app that runs code on the storefront and is installed outside the organisation. On 1 January 2027 a public app that runs code on the storefront and has not declared its network access is delisted and blocked from new installs. The existing install keeps working. Until every custom storefront app already installed outside the organisation has declared it, no new install can be made outside the organisation. On 1 March 2027 Shopify stops injecting script tags into storefronts. The script moves into an app embed in a theme app extension, or into a web pixel for analytics. An admin-created custom app cannot use an extension, so the script moves into the theme. That calendar meets the checkout phishing below at the same door: whoever can write code onto the page the customer sees can also change where the checkout button goes first.

### Which steps should an agency take before a release?

Start with the app that can pull the most data. The ones that run bulk operations go to the top of the list.

1. **Write down every app in the organisation.** Match the Partner Dashboard and Dev Dashboard lists to the stores they are installed on. Put the bulk-operation apps first. Talk, in this pass, about closing any app nobody owns.

2. **Test the last 30 days before you turn the IP allowlist on.** If egress is fixed, write the IPs. If you need an ASN, limit it by country. If your own server would be blocked in the test, do not turn enforcement on. On a public app the list is the condition for bulk operations and for new installs.

3. **Enable bulk operations only where there is a job.** Turn the query and the mutation on separately. Confirm in the dashboard that apps already running them stayed enabled. Put a reminder next to a job that runs less often than every 31 days. When access drops, the job fails as access denied.

4. **Audit outside installs before 1 January 2027.** Every custom app sitting on a store outside the organisation should have a list. If one is missing, none of your apps can be installed outside the organisation after that date. A store inside your own organisation is outside this rule. Turn the list on there anyway.

5. **On a migrated custom app, set the list and the newer authentication with the merchant.** Tell the store owner the token did not change on its own. Uninstall the one nobody uses. Rotate the token of the one you still use, and see the old value return 401. On a client transfer store that has not moved and has not been transferred, do not keep the token in code, a repository or a handoff file.

6. **Run the app security check before every release.** `shopify app security check` looks for Shopify-specific findings such as an endpoint that does not authenticate, a secret committed to the repository, and a query that is not limited to one store. Include a separate backend that touches merchant data. The check does not cover hosting, accounts or the habit of reading logs. Those stay on your list. The detail is on the [app security checks](https://shopify.dev/docs/apps/build/security/app-security-checks) page.

7. **Rotate a secret that has lived in code, a repository or a handoff document.** For a client secret, Shopify's order, when you want to avoid downtime, is this: generate the new secret, make webhook checks accept both, move stored tokens onto the new secret, and only then revoke the old one. If it is being misused, revoke first. Downtime is lighter than leaving a leaked key working. An admin-created app that has not moved yet cannot rotate its client secret. On that app a new token comes from uninstalling and reinstalling. The steps are in the [credential rotation](https://shopify.dev/docs/apps/build/authentication-authorization/client-secrets/rotate-revoke-client-credentials) document.

8. **Close accounts and spare access.** Shopify wrote, as of the 19 November 2026 update, that multi-factor authentication is required on every partner account, and it recommends passkeys. Apply the same discipline to hosting, DNS, source control and email. Remove a leaver's access the same day. Drop a scope the app no longer calls.

### What should a store owner ask their agency?

The answer should not be "we are secure". Ask which app, which date, which screen. Ask for the answer in writing.

- On which of your apps is the IP allowlist on, and on which is it off? Start with the ones that run bulk operations.
- Where are bulk queries and bulk mutations enabled? Did both start in the last 31 days, and will a rare job lose access?
- Do the custom apps we opened under Develop apps now appear in the Dev Dashboard? Did the token change on its own, and is the allowlist on?
- On a client transfer store that has not been transferred yet, is the token sitting in a handoff document, a repository or an email?
- Did `shpat_`, `shppa_` or a client secret turn up in the theme, the repo or an old handoff note? If it did, does the old value now return 401?
- Did the app security check run before the last release, and is any finding still open?
- Is there a passkey or two-step verification on the partner, hosting, DNS, source control and email accounts? Is a leaver's access closed?
- On an app you will create after 1 December 2026, have you moved to an expiring token? On a public app, is the migration done before the 1 January 2027 delisting date?

## What happens if a Shopify app is hacked?

When an app is hacked, the storefront may not be taken over. What is taken is usually the token the app received from Shopify. A token is a credential that goes out with every API request. The scopes on it limit what that request can read and write. `read_customers` is enough to read a customer record. `read_orders` is enough to read an order. The payment card may stay on Shopify's card side. The app can still pull name, email, phone, address and order total without ever seeing that side. The Sneak Energy notice is the example of this split: no payment details and no password, and the address and total spend are there.

The Swym incident shows the second shape. An app configuration can push a script onto the storefront. The visitor sees a normal page and, on the checkout button, goes somewhere else. Customer data can leave from the app's database, and it can also be typed by the customer on the page they were sent to. Those are separate incidents. The answer to the first is to end the token. The answer to the second is the phishing check below.

### How do you revoke a Shopify access token?

There are three paths. All three rest on the uninstall and revoke lines in Shopify's token document.

First, uninstall the app under Settings, then Apps and sales channels. That app's tokens on this store end. Do not delete an app you still use in a panic. If there is an incident, read the vendor's instruction first. Swym revoked its own access. A script in the theme file may still be there. Search for it separately.

Second, if the vendor revokes the client secret, tokens minted with that secret become invalid. The next request returns 401. A button in the store admin does not do this. It is the vendor's job. Ask the vendor whether the secret was rotated, and whether the old token now returns 401. If an allowlist is on, a test from a machine outside the list returns 403. A 403 does not mean the token is dead. Look for the 401 from the app's own server, or from inside the list.

Third, your own custom app. You will see it under Apps and sales channels as well. If nobody uses it, uninstall it. If you use it, rotate the Admin API token. If the admin has no rotate control, uninstall and reinstall an admin-created app to take a new token. Check that a request made with the old value no longer passes. The old token may still sit on an agency laptop, in a backup file or in a chat log. Rotation closes that copy too. Changing only the staff password leaves the token where it is. A move to the Dev Dashboard leaves the token where it is as well.

## How do you spot checkout phishing?

The customer is on your storefront. They put a product in the cart and press Checkout. Shopify's checkout page should open on the store's own domain, or on the store's myshopify.com address. In the phishing pattern, the button sends the browser somewhere else before that page can open. The page looks like Shopify checkout. The card is typed there. The browser can then move on to the real checkout, and an order can still be placed. The customer takes the first page for a glitch.

[Fudge's account of 19 October 2026](https://www.fudge.ai/blog/shopify-checkout-phishing-attack/) describes this pattern as a campaign seen on 10 October 2026, while a developer was buying from a store. The code is not inside Shopify's checkout page. It is on the storefront, on the click that leads to the checkout button. The same piece reports that Hulk Product Options and Selleasy also said an unauthorised party had changed what their apps loaded on some storefronts. Swym's own FAQ is a documented link in that pattern: on 14 October an unauthorised script entered the configuration, the script ran on the checkout click rather than on page load, and the company stopped the app on every store and revoked its Shopify access.

![Flow from the storefront through an injected script to a fake checkout domain](https://nodusworks.com/blog/shopify-guvenlik-rehberi-2026/odeme-oltalama.webp)

The script reaches the store by two paths. On one, the clean file the app places on the storefront asks the vendor's server for that store's settings. The bad code sits inside the settings. Searching the theme files will not show it, because the theme never changed. On the other, the app uses its own access to the store and writes a script into the theme. Swym asking merchants to search theme files for `checkout-guard.top` fits this second path. Swym writes that it saw no finding that the real checkout form was read. In the campaign Fudge describes, the card is typed on the outside page before the real checkout opens. The two do not cancel each other. If there was a redirect, the card risk stands apart from the vendor's sentence that they did not read the checkout fields.

Customising the checkout page on a Shopify Plus store is a separate job, and [Shopify Plus solutions](https://nodusworks.com/en/services/shopify-plus-solutions) look at that layer. The phishing happens on the click before that page opens. Painting the page itself does not close a script an app placed on the storefront.

What to look at this afternoon:

- In a private window, put a product in the cart. Press the store's own Checkout button. Do not use Shop Pay, PayPal or another express option for this test. The moment the page opens, the address should be your store's domain or myshopify.com. Another domain, especially a `.top` address that reads like billing, checkout or account, is the stop sign. Do not type a card.
- Repeat the same test from the button in the cart drawer, and on a phone. Because the script can fire once per session, a normal window you have already browsed in can hide it.
- Search the theme for `checkout-guard.top`, `account-confirm.top`, `billing-confirm.top` and `checkout-secure.top`. The researcher note that Fudge relays also says `biliing.top`, `checkout-confirm.top` and `order-confirm.top` were seen in this campaign. Do not go to these addresses.
- Online Store, Themes, the live theme, Customize, then App embeds. Turn off an embed you cannot name. Code that arrives from inside settings does not show up in a theme search. A clean theme does not clear a storefront app.
- Ask people who ordered in the last few days: did checkout ask for the card on an address they did not recognise, or did it ask for the card twice? Follow a vendor notice that arrived, and still do the click test.

If you suspect it, set the order the way Shopify's incident document does. Turn the script off, cut the app's access the way the vendor describes, keep a copy of the theme before you delete anything, and write to <security@shopify.com>. If a customer typed a card, tell them to cancel it with their bank and to type the store address themselves. A link inside a surprise "your payment could not be verified" message is the continuation of this incident.

## Where does the risk around the store come from?

Shopify's core is not a server you patch. The path to customer data can still sit somewhere outside the store: the app's backend, the agency's tools, a headless storefront, the brand's WordPress site, a host that keeps the token as an environment variable. Three developments on those layers have been confirmed in recent months.

### How is AI speeding attacks up?

Shopify's app security page writes that agents can find a weakness in minutes, and that the same capability is open to the attacking side. The [summary of Microsoft's Digital Defense Report of 1 October 2026](https://www.microsoft.com/en-us/security/security-insider/threat-landscape/2026-digital-defense-report) says the median time from a weakness seen in the wild to weaponisation has fallen to well under 24 hours, while closing a critical, internet-facing weakness can take an organisation 30 to 60 days. The same summary says AI is being used in vulnerability discovery, reconnaissance, phishing, malware and exploit development. Most complex intrusions still have a person directing them. What got shorter is the specialist time that used to be scarce.

On the phishing side, a [2026 note from Google's Threat Intelligence Group](https://cloud.google.com/blog/topics/threat-intelligence/agentic-threat-activity-crosses-a-significant-threshold/) says the Jieyou service, first seen in March 2026 and focused on e-commerce fraud, added a chat assistant in June 2026. A low-skill user changes the phishing page in the panel with an ordinary sentence. A checkout page that looks like your storefront no longer has to be built by hand, one page at a time.

The link for a store is this. Shopify itself does not have to be the product that gets hacked at that speed. A trusted app's token, a secret in the agency's repository, and the domain the checkout button goes to can all be reused the same day. Microsoft's summary puts it as following trust: a valid credential makes bad traffic look like legitimate traffic. A token that carries `read_orders` does exactly that.

### Why do PHP flaws matter to a Shopify store?

[CISA's alert of 21 October 2026](https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching), updated on 26 October 2026, named CVE-2026-109618 and CVE-2026-109619 as php2shell. Both allow unauthenticated remote code execution. CISA added both to its [known exploited vulnerabilities catalogue](https://www.cisa.gov/news-events/alerts/2026/10/26/cisa-adds-two-known-exploited-vulnerabilities-catalog) the same day. What is affected is a PHP install that serves web requests: Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. The patched versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older are unsupported. CISA says to take those systems offline until they can be patched. PHP often sits inside other software and is not obvious from the outside.

You do not apply this patch to the core of a Shopify store. You apply it to the same brand's WordPress, the PHP layer of a headless storefront, an internal agency tool, and an app server written in PHP. If a shell opens there, the Shopify token in the environment can be read too. An entry in the catalogue is not closed by the sentence "our stack is not PHP". Ask whether the inventory has PHP in it.

### Where was the token in the Railway incident?

[Railway's incident report of 10 November 2026](https://blog.railway.com/p/incident-report-october-security-incident) describes access that began at 07:28 UTC on 20 October 2026 and ended when the attacker was removed from the systems at 09:24 UTC on 21 October 2026. The attacker was able to decrypt some environment variables in at most 1.85 percent of workspaces, about 100,000 workspaces. The report writes that figure as an upper bound, not as a count of confirmed thefts. The queries favoured AI provider keys. A further query also matched cloud, database and payment-service credentials. The report says they saw no sign that customer databases were accessed. Among what was decrypted were linked-account tokens for 1,852 users. Railway reset those, notified the users, and estimated unauthorised spend at about 740,000 dollars. At 20:19 UTC on 21 October 2026 every user session was invalidated. Customers assessed as high risk were written to separately.

Shopify checkout was not the target of this incident. The target was the platform that holds an app's secrets. If your custom app runs on Railway and an Admin API token or a client secret sat in an environment variable, and Railway wrote to you as high risk, or you cannot show that the workspace was outside this set, rotate that secret. Check that the old value no longer works. A project that was not notified, and that does not keep a Shopify secret in a variable, does not become a breach by this paragraph alone.

## Which 12 steps harden a Shopify store?

The right order is to list what is there before you delete anything, and to know what each removal closes. Admin paths are written for the English admin interface.

1. **Uninstall apps you do not use.** Under Settings, then Apps and sales channels, remove the app nobody opens. Uninstalling ends that app's tokens on this store. Write down the name and the date.

2. **Remove sales channels and online channels you do not use.** On the same screen, close a channel you no longer sell on. If the channel is installed as an app, removing it ends those tokens too.

3. **Review staff accounts and remove people who have left.** Under Settings, then Users and permissions, match every name to someone who still works. Remove the person who left, narrow the permission to the job, and do not share a login.

4. **Remove collaborator accounts you do not need, and require the request code.** A collaborator is partner access given without a staff card. Remove an account you do not recognise. Keep the collaborator request code on. If the code is sitting in plain text in an email, rotate that too.

5. **Turn on two-step verification for every staff account.** On the same screen, check that it is on for every account. Swym also recommended two-factor authentication after the incident. Turn it on immediately wherever it is off. On the agency's partner accounts, Shopify wrote as of 19 November 2026 that multi-factor authentication is required.

6. **Rotate the custom app token, or delete the app.** Uninstall a custom app nobody uses. Rotate the Admin API token of the one you use. If the admin has no rotate control, uninstall and reinstall to take a new token. A move to the Dev Dashboard does not change the token. A request made with the old value should return 401. The detailed search is the token list below.

7. **Keep scopes to the size of the job.** `read_customers` and `read_orders` are enough to read customers and orders. On a custom app, remove a scope nothing calls. If an App Store listing is wider than the job, ask the vendor before you approve it.

8. **Have an AI scan the theme and the custom app source, then have a person read it.** Do not paste code into a chat without masking the key. On the masked copy, search for tokens that start with `shpat_` and `shppa_`, for a client secret, for a script you do not recognise, and for the domains Swym published. A person should read every line that gets flagged.

9. **Look for a script or an embed in the theme that you do not recognise.** Online Store, Themes, the live theme, Customize, then App embeds. Turn off an embed you cannot name. With Edit code, search for `checkout-guard.top`, `account-confirm.top`, `billing-confirm.top` and `checkout-secure.top`. Swym writes that Shopify keeps an older version of the theme. Keep the file before you delete it. Trying the theme somewhere other than the live copy is the subject of the [backup theme and safe development guide](https://nodusworks.com/en/blog/shopify-backup-theme-guide). Keeping a copy of data that gets deleted is covered in the [store backup guide](https://nodusworks.com/en/blog/shopify-store-backup-guide).

10. **Ask every app vendor for a report and a written commitment.** Send the text below to their support address. If no answer comes, do not mark the app clean. Keep the answer under the app's name.

11. **Warn your customers about phishing.** If a notice arrived, write what was exposed according to the text you received. The Sneak Energy frame is one example: name, email, phone, address and total spend may be there, and payment details and the password may not. The store does not ask you to confirm an address or a payment through a surprise message. Customers should type the site address themselves.

12. **Write four names into the incident plan.** Who uninstalls the app. Who closes staff and collaborator access. Who saves the theme version and the installed app list before anything is deleted. Who writes to the vendor and, if needed, to <security@shopify.com>. Shopify's order: contain, revoke credentials, keep the logs, write to that address, identify the affected data, close the root cause, meet the legal notice. Walk the plan once a year.

## How do you find an unused or leaked token?

This list turns step 6 of the 12 into something you can do. Uninstalling an app ends the token on Shopify's side. The copy in the theme, the repository and the handoff note stays until you rotate it.

1. **Write down the apps and the custom apps.** Note the name of every row under Settings, then Apps and sales channels, who installed it, and whether it still does a job. Add the legacy custom apps under Develop apps, and the moved copies that appear in the Dev Dashboard. Sales channels belong on this list too.

2. **Check the last API use, where you can see it.** If a migrated custom app, or an app in the Dev Dashboard, has API logs, look at the date of the last call and the source address. An address you do not recognise is a sign the token was used from another network. If there is no log, ask the partner who holds the app for the date of the last call, in writing. Use you cannot see is not the same as "unused".

3. **Search the theme, the code, the repository and the handoff documents for the prefixes.** Search the live theme, old theme copies, Git history, CI variables, email attachments and the agency's handoff note for `shpat_` and `shppa_`. Search for the client secret that sits next to a client ID as well. Mask the value before you paste it into a chat window. Write down the path and the date of every file you find.

4. **Match collaborator and staff accounts.** Under Settings, then Users and permissions, hold every name against someone who works today. Remove the person who left. Keep the collaborator request code on. A party who does not know the code cannot send an access request.

5. **Rotate.** Uninstall the app nobody uses. That ends the app's tokens on this store. On a custom app you still use, take a new Admin API token. On an admin-created app the path is uninstall and reinstall. If the app is in the Dev Dashboard, rotate the client secret so that stored tokens move onto the new secret before you revoke the old one. Do not write the new value into the document where you found the old one. Put it in a password manager.

6. **See the old value return 401.** An Admin API request made with the old token should return 401. If you see 403, the request may have left from a network outside the IP allowlist. That result does not show the token is dead. Repeat the test from inside the list, which means from the app's own server. If 401 arrives there as well, the old copy is closed.

7. **Write it down.** Keep a note of which app you rotated, the date, that the old value returned 401, and who holds the new value. Do not write the token itself into the note. The person who uninstalls the app and the person who would write to <security@shopify.com> should both be able to see the note.

### Which security questions should you ask apps?

The table below is the skeleton of the email you send in step 10. Each row matches a fact that was missing this autumn. Triple Whale did not explain the way in, the data types or the store count. Swym wrote that it saw no data leak inside the app, and it named the redirected shopper as a separate risk. Ask the vendor for a sentence at that level of clarity.

| Question                                                                           | Why it matters                                                                                                                    |
| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| When was your last independent security assessment, and will you share the report? | A date and a report do more work than the sentence "we are secure".                                                               |
| Have you had an incident in the last 24 months, and when were stores told?         | Triple Whale's detection was 31 October, the public statement 20 November. The delay is why the question is asked.                |
| Which Shopify scopes do you request, and which customer fields do you store?       | `read_customers` and `read_orders` are enough to read a name, an address and an order.                                            |
| After we uninstall, how long does our data stay with you?                          | Uninstalling ends the token on Shopify. It does not delete the vendor's copy.                                                     |
| Where do the access tokens live, and who can read them?                            | A token is a key. The system that holds the keys is the door to the store.                                                        |
| Which addresses does your IP allowlist cover, and is bulk operations on?           | An Admin API request from outside the list returns 403. If a bulk operation does not start for 31 days, access to that type ends. |
| Have you moved to expiring offline tokens?                                         | On new apps the lifetime is one hour. An expiring token stops being useful soon, even if it leaks.                                |
| Will you give this as a written commitment in an email or a contract?              | A spoken assurance cannot be attached to a customer notice. A written sentence can.                                               |

The short text you can send is below. It is a template. It is not an answer a vendor has already written to you.

> Subject: Security information request, \[store name]
>
> Hello,
>
> \[App name] is installed on the \[store name] Shopify store. After the app incidents of autumn 2026 we want the following in writing: the date of your latest security report, your incident and notification history over the last 24 months, the Shopify scopes you request, the customer fields you store, how long you keep data after we uninstall, where the tokens live, which addresses your IP allowlist covers, and whether bulk operations are enabled. We will keep these answers as a security commitment.
>
> Thank you, \[name, role]

If no answer comes, do not mark the app clean. Write "no answer" on the list and think again about uninstalling it.

## Who can run the security review?

A store owner can work through this list alone. For a second pair of eyes, Nodus Works' [Shopify technical support and maintenance](https://nodusworks.com/en/services/shopify-technical-support-maintenance) reviews installed apps, staff and collaborator accounts, custom app tokens, the IP allowlist and theme embeds in the same order, and delivers the findings as a written report. If you would rather talk for 30 minutes first, [book a meeting](https://nodusworks.com/en/contact#toplanti).

## Frequently asked questions

### Was Shopify hacked?

The three incidents in this article do not say that Shopify itself was hacked. Triple Whale identified unauthorised access to certain of its internal systems. Swym said an unauthorised script was introduced through the Wishlist Plus configuration. At IMADEYA, order and customer data was read with the Admin API token of the store's own custom app. A storefront that loads does not mean the customer data is still only where you left it.

### I use Triple Whale. What should I do?

Under the 20 November 2026 statement, if you have not received a notification, no action is required on your Triple Whale account. Search your inbox for the company name. Do not click a notice that arrives as a surprise link. If a notice did arrive, tell your customers, in your own words, which fields it lists, and warn them about phishing. The forum claim of 91,310 tokens and 20,510 stores has not been confirmed by Triple Whale or by Shopify. In either case, uninstall apps you do not use and review custom app tokens.

### How do you revoke a Shopify access token?

Uninstalling the app under Settings, then Apps and sales channels, ends that app's tokens on this store. If the vendor revokes the client secret, tokens issued with that secret end as well, and requests return 401. On your own custom app, delete the one nobody uses. Rotate the Admin API token of the one you still use, and check that the old value no longer works.

### Is uninstalling the app enough?

Uninstalling ends the token on Shopify's side. It does not delete a copy of customers or orders the app already pulled into the vendor's systems. As in the Swym incident, a script written into the storefront may not disappear on its own. Ask the vendor how long they keep data. Separately, search the theme for a script or an app embed you do not recognise.

### What is a collaborator?

A collaborator is partner access given to the store without opening a staff account. Agencies and freelancers usually come in this way. Under Settings, then Users and permissions, remove collaborator accounts you do not recognise, and require the collaborator request code. A party who does not know the code cannot send you an access request.

### Is two-step verification mandatory?

It should be on for every staff account. Swym recommended two-factor authentication to merchants after the Wishlist Plus incident. Shopify wrote, in its 19 November 2026 update, that multi-factor authentication is required on partner accounts, and it recommends passkeys. Find the store accounts where it is off in Settings, Users and permissions, and turn it on. Ask about the agency's partner, hosting, DNS, source control and email accounts as well.

### What is an IP allowlist, and does it affect my store?

An IP allowlist limits the addresses from which an app's token can call the Admin API. With enforcement on, a request from outside the list returns 403. Since 20 November 2026 a public app with no allowlist is delisted from the App Store and cannot take new installs. The existing install keeps working. A custom app installed on a store outside the organisation also needs a list for a new install. On 1 January 2027, if any of those outside installs has no list, the organisation cannot install an app outside it. An app created in the admin that has not yet moved to the Dev Dashboard cannot use a list.

### Why do bulk operations start off?

A bulk operation is a bulk query or a bulk mutation that reads or writes many records at once. Since 6 November 2026, apps a partner builds cannot run either type until that type is enabled on its own. Apps that were already running them were left enabled. If a type does not start for 31 days, access to that type ends. The 30 days mentioned in the email is not the number in the document. The 19 November 2026 update says merchant-created custom apps must enable this access from the Dev Dashboard settings as well.

### Does my token break when an old custom app moves to the Dev Dashboard?

No. Shopify is moving custom apps created under Develop apps in the admin to the Dev Dashboard. A moved app keeps its installation, its scopes and its existing Admin API token. The move does not rotate the token and does not turn the IP allowlist on. An app that has not moved yet stays in the admin, and its client secret cannot be rotated there. The partner note that reached Nodus Works says these apps, on client transfer stores that have not yet been transferred, stay in the admin for now. That token should not live in code, a repository or a handoff document.

### How do I notice checkout phishing?

In a private window, put a product in the cart and press the store's own checkout button. The moment the checkout page opens, the address should be your store's own domain or its myshopify.com address. Another domain, especially a .top address that reads like billing, checkout or account, is the phishing sign. Do not type a card. Repeat the test from the cart drawer and on a phone. Search the theme for checkout-guard.top, account-confirm.top, billing-confirm.top and checkout-secure.top. A clean theme does not rule out a script sitting in the app's own settings.

## Sources

- Triple Whale's statement of 20 November 2026: [post on X](https://x.com/triplewhale/status/2123848682646765890)
- Swym Wishlist Plus incident FAQ, 20 October 2026: [getswym.com](https://www.getswym.com/resources/wishlist-plus-incident-faq)
- Shopify access token document: [Access tokens](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens)
- Shopify incident response document: [Respond to a security incident](https://shopify.dev/docs/apps/build/security/monitoring-and-response/respond-to-a-security-incident)
- Enabling bulk operations, 6 November 2026: [Partner apps must enable bulk operations before use](https://shopify.dev/changelog/posts/partner-apps-must-enable-bulk-operations-before-use)
- Bulk operations document, the 31-day rule: [Bulk import data with the GraphQL Admin API](https://shopify.dev/docs/apps/build/apis/graphql-admin/bulk-operations/imports)
- IP allowlist: [Restrict API access with an IP allowlist](https://shopify.dev/docs/apps/build/dev-dashboard/ip-allowlist)
- Allowlists for public apps, 5 November 2026: [IP allowlists are now required for public apps](https://shopify.dev/changelog/posts/ip-allowlists-are-now-required-for-public-apps)
- Allowlists for custom apps outside the organisation: [IP allowlists for custom apps](https://shopify.dev/changelog/posts/ip-allowlists-are-now-required-for-custom-apps-installed-outside-your-organization)
- Security calendar and the note on AI: [About app security](https://shopify.dev/docs/apps/build/security)
- Update of 19 November 2026, bulk operations on merchant custom apps and MFA on partner accounts: [IP allowlist due tomorrow](https://shopify.dev/changelog/blog/app-security-updates-ip-allowlist-due-tomorrow)
- Admin-created custom apps moving to the Dev Dashboard, 17 November 2026: [Admin-created custom apps](https://shopify.dev/changelog/posts/admin-created-custom-apps-are-now-built-and-managed-in-the-dev-dashboard)
- Maintaining an app that has not moved yet: [Maintain admin-created custom apps](https://shopify.dev/docs/apps/build/authentication-authorization/legacy/admin-custom-apps)
- Scan before release: [App security checks](https://shopify.dev/docs/apps/build/security/app-security-checks)
- Client secret rotation: [Rotate or revoke client credentials](https://shopify.dev/docs/apps/build/authentication-authorization/client-secrets/rotate-revoke-client-credentials)
- Expiring token calendar: [Migrate to expiring offline access tokens](https://shopify.dev/docs/apps/build/authentication-authorization/migrate-to-expiring-offline-access-tokens)
- Partner Town Hall, H2 2026: [shopify.com/webinar/partnertownhall-h2-2026](https://www.shopify.com/webinar/partnertownhall-h2-2026)
- Checkout phishing pattern, 19 October 2026: [Fudge](https://www.fudge.ai/blog/shopify-checkout-phishing-attack/)
- Roundup of 21 November 2026, the Triple Whale statement and the Sneak Energy notice: [HackerMe Security](https://security.hackerme.ai/shopify-app-hacked-customer-addresses/)
- Summary of the IMADEYA incident, 26 October 2026 (Japanese): [Self Plus](https://self-plus.co.jp/knowledge/shopify-news/imadeya-shopify-custom-app-admin-api-token-leak-2026-10/)
- Microsoft Digital Defense Report summary, 1 October 2026: [Security Insider](https://www.microsoft.com/en-us/security/security-insider/threat-landscape/2026-digital-defense-report)
- Google Threat Intelligence, e-commerce phishing service: [Agentic threat activity](https://cloud.google.com/blog/topics/threat-intelligence/agentic-threat-activity-crosses-a-significant-threshold/)
- CISA, PHP patch, 21 October 2026, updated 26 October: [Critical vulnerabilities in PHP](https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching)
- CISA KEV, 26 October 2026: [CVE-2026-109618 and CVE-2026-109619](https://www.cisa.gov/news-events/alerts/2026/10/26/cisa-adds-two-known-exploited-vulnerabilities-catalog)
- NVD: [CVE-2026-109618](https://nvd.nist.gov/vuln/detail/CVE-2026-109618), [CVE-2026-109619](https://nvd.nist.gov/vuln/detail/CVE-2026-109619)
- Railway incident report, 10 November 2026: [October 21st security attack](https://blog.railway.com/p/incident-report-october-security-incident)

---

Source: [Shopify Security Developments and Hardening Guide 2026 · Nodus Works](https://nodusworks.com/en/blog/shopify-security-guide-2026)  
Full content index: https://nodusworks.com/llms.txt  
MCP server for AI agents: https://nodusworks.com/en/ai-mcp
