Shopify Security Developments and Hardening Guide 2026

A storefront drawn in thin ink on warm paper, with a green shield and a padlock

In autumn 2026 the weak point of a Shopify store was often a connected app and its token. Three incidents, the scopes that matter, and a 12-step hardening list.

Published 17 min read

The common point of the three security incidents that became public in October and November 2026 was not the store password, but 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.

This guide is current as of 22 November 2026. It tells the incidents from the companies' own statements, and it marks unverified forum claims clearly as claims.

Is my Shopify store safe?

Short answer: Shopify itself was not hacked in these incidents, but your store is only as secure as your installed apps, staff accounts and tokens. What was exposed 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.

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?

If you can't answer even one of these clearly, start with the 12-step list below.

What happened to Shopify stores in autumn 2026?

In all three, not Shopify's infrastructure but an app the store trusted, or the store's own custom app token, was the path to customer and order data. The table contains only officially disclosed information.

IncidentDateWhat happenedLesson for the store
Triple WhaleFound 31 October 2026, contained 1 November 2026, statement 20 November 2026The analytics app said it found unauthorised access to certain internal systems. Impacted parties were notified.If you received no notice, no action is required on your Triple Whale account. Data types and store counts were not disclosed.
Swym Wishlist PlusScript on 14 October 2026, FAQ on 20 October 2026An unauthorised configuration change loaded a script on a limited set of storefronts that tried to redirect shoppers when they clicked checkout. The app was paused for every merchant, Shopify access was revoked, and credentials were rotated.Check theme files and app embeds. The detail is on Swym's own FAQ.
IMADEYADisclosed 15 October 2026A third party obtained the Admin API token of the Japanese store's own custom app. Order and customer data was read from foreign IP addresses. Card data was not leaked.A custom app token is a key of its own, separate from a staff password.
Shopify token docsCurrent text, read 22 November 2026Uninstalling an app ends all of that app's tokens for the store. Revoking the client secret invalidates tokens issued with it. Requests then return 401.Incident order: contain, revoke credentials, preserve logs, write to security@shopify.com.

What did Triple Whale disclose?

On 20 November 2026 Triple Whale wrote on X that on 31 October 2026 it identified unauthorised access to certain of its internal systems. The incident was contained on 1 November 2026. The investigation was completed with third-party cybersecurity experts. Based on that investigation, impacted parties were notified. The company also said it had taken additional steps to strengthen the security of its systems.

The sentence that matters for a store owner is the company's own English: "If you have not received a notification from us, there is no action required on your Triple Whale account." The statement does not describe the entry method, the types of data taken, or the number of stores affected.

Sneak Energy told its own customers that names, emails, phone numbers, addresses, and total spend had been exposed, and that payment details and passwords were not part of that exposure. That list is not Triple Whale's public statement. It is the notice that merchant sent to its customers. It does not follow that every store using Triple Whale lost the same fields. If you did not receive a notice, do not copy Sneak Energy's list onto your own store. Search your inbox for the company name. Do not click a notice that arrives as a surprise link.

On 11-12 November 2026 a post on a dark-web forum claimed that Triple Whale's internal database included 91,310 Shopify tokens across 20,510 stores, and that most of those tokens had been rotated. Triple Whale has not confirmed those numbers. Shopify has not confirmed them either. The post is a claim. This guide does not use those numbers as the measure of the incident.

What happened at Swym Wishlist Plus?

Swym's incident FAQ, dated 20 October 2026, says that on 14 October 2026, between 10:06 and 11:56 UTC, an unauthorised change was made to the Wishlist Plus configuration. The change loaded a script on a limited subset of storefronts using the app. The script did not run on its own when the page opened. It fired when a shopper clicked a checkout button, and it tried to send the shopper away from the store. Swym writes that it has not found evidence the script read form fields on the genuine storefront or on Shopify checkout pages.

Swym paused the app for every merchant at once, not only for stores it already knew were affected. It revoked Shopify access for Wishlist Plus and for its other apps. It rotated credentials. The company says it has found no evidence that merchant data or customer personal information was compromised inside the app. If a redirected shopper typed details into an external site by hand, that entry is a separate risk. Swym says that too.

Swym says it contacted affected stores directly. To check for yourself, search the theme files for checkout-guard.top and for edits made by the Swym app that you do not recognise. On the same page, Swym also shares account-confirm.top, billing-confirm.top and checkout-secure.top as domains seen in similar attacks, and worth monitoring.

What was disclosed about IMADEYA?

In the IMADEYA incident disclosed on 15 October 2026, a third party obtained the Admin API access token of a Japanese store's own custom app. The token was used from foreign IP addresses to read order and customer data. What was read includes names, emails, order numbers, and amounts. Card data was not leaked. 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 can end up pasted into a theme file, an email, or an old agency's notes. The custom app development guide covers token types in detail. This article does not repeat that 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 documentation states two rules plainly. When a merchant uninstalls an app, access ends for all of that app's tokens on that store. When the app's client secret is revoked, access ends for the tokens the app 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 same page says offline and online access tokens begin with shpat_. Searching theme and custom app code for that prefix is a shorter path than scanning for a leaked key by eye.

Shopify's incident response document sets this order at the first sign of trouble: contain the incident, revoke exposed credentials, tokens and sessions, preserve logs before they are deleted, and write to security@shopify.com. Then identify the affected stores and data, fix the root cause, and meet the legal notification duties. The document is written for app developers; on the store side, the equivalent is the incident plan in step 12.

What is Shopify changing in 2026?

Alongside the incidents, Shopify is tightening token security. According to the access token documentation:

  • Creating custom apps in the admin is closed. Older custom apps created in the admin keep working, but a new one can no longer be opened. If you still have one, it matters even more who holds its token.
  • Expiring tokens are becoming required. Every app created on or after 1 December 2026 must use offline tokens that expire after one hour. For public apps, that rule began on 1 April 2026.
  • Public apps that still use non-expiring tokens are being removed. They will be delisted and blocked from new installs on 1 January 2027, and their API requests will be rejected from 1 April 2027.
  • An IP allowlist limits a leak. Once an allowlist is in place, tokens only work for Admin API requests from the listed addresses.

For a store owner, the practical result is to ask each installed app's vendor whether they have moved to expiring tokens. That question is worth adding to the security questions table below.

What happens if a Shopify app is hacked?

When an app is hacked, the storefront itself may stay in your hands. What often leaves is the token the app received from Shopify. A token is a credential sent with each API request. The scopes on it limit what that request can read or write. read_customers is enough to read customer records. read_orders is enough to read orders. The payment card can still sit on Shopify's card side. The app can still pull names, emails, phone numbers, addresses, and order amounts without ever seeing that side. The Sneak Energy notice is an example of that split: no payment details and no passwords, and addresses and total spend present.

The Swym incident shows a second shape. The app configuration can push a script onto the storefront. The visitor sees a normal page, then a checkout click sends them elsewhere. Customer data can also leave from the app's own database, or the customer can type it on the page they were sent to. Those are separate events.

A doorway on warm paper, with three keys beside it

How do you revoke a Shopify access token?

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

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

Second, if the app vendor revokes the client secret, tokens issued with that secret stop working. 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.

Third, your own custom app. You will see it under Apps and sales channels as well. If nobody uses it, uninstall it. If you still use it, rotate the Admin API token. Check that a request made with the old value no longer succeeds. The old token may 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.

What 12 steps harden a Shopify store?

The right order is to list the current state before deleting anything, and to know what each removal closes. Admin paths follow the English Shopify admin.

A blank sheet of paper, a fountain pen, and a small shield
  1. Uninstall apps you do not use. In 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 unused sales channels and online channels. On the same screen, close a channel you do not sell on. If the channel is installed as an app, removing it also ends those tokens.

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

  4. Remove collaborator accounts you do not need, and require a request code. A collaborator is partner access without a staff seat. Remove an account you do not recognise. Turn on the collaborator request code. If the code sits in plain text in an email, rotate it.

  5. Turn on two-step verification for every staff account. Check that every account has it on. Swym also recommended two-factor authentication after the incident; turn it on immediately wherever it is off.

  6. Rotate the custom app token, or delete the app. Remove a custom app nobody uses. Rotate the Admin API token of one you still use; if the admin offers no regenerate option, uninstall and reinstall the app to get a new token. A request with the old value should return 401. Do not paste the token into a theme, a backup file, or a chat.

  7. Keep scopes to the job. read_customers and read_orders are enough to read customers and orders. On your own custom app, remove a scope the integration never calls. If an App Store list is wider than the job, ask the vendor before you approve it.

  8. Have the theme and the custom app source scanned by an AI, then by a person. Do not paste a live key into a chat. On a masked copy, search for tokens that start with shpat_, API keys, the client secret, scripts you do not recognise, and the domains Swym published. A person should read every line the model flags.

  9. Check the theme for unknown scripts and embeds. In Online Store, then Themes, open Customize on the live theme, then App embeds. Turn off an embed you cannot name. In Edit code, search for checkout-guard.top, account-confirm.top, billing-confirm.top, and checkout-secure.top. Swym's FAQ says Shopify keeps older theme versions. Save the file before you delete anything. A separate frame is the Shopify store backup guide.

  10. Ask every installed vendor for a report and a written commitment. Send the note below to each support address. If no reply comes, do not treat the app as clean. Keep the reply next to the app's name.

  11. Warn customers about phishing. If you were notified, tell them what was exposed, using the notice you received. The Sneak Energy split is one frame: names, emails, phones, addresses, and total spend can be in a notice, while payment details and passwords are not. The store will not ask them to confirm an address or a payment from a surprise message. They 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 app list before anything is deleted. Who writes to the vendor and, if needed, to security@shopify.com. Shopify's order is: contain, revoke credentials, preserve logs, write to that address, work out which data was affected, fix the root cause, and meet the legal notice. Walk through the plan once a year.

Which security questions should you ask an app?

The table below is the skeleton of the email in step 10. Each row matches something this autumn left unanswered. Triple Whale did not disclose the entry path, the data types, or the number of stores. Swym said it saw no data leak inside the app, and it separately described the risk for a shopper who was redirected. Ask the vendor for sentences that clear.

QuestionWhy it matters
When was your last independent security assessment, and will you share the report?A date and a report do more work than "we are secure."
Have you had an incident in the last 24 months, and when were merchants told?Triple Whale found the access on 31 October and published the statement on 20 November. The delay is why you ask.
Which Shopify scopes do you request, and which customer fields do you store?read_customers and read_orders are enough to read names, addresses, and orders.
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 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.
Have you moved to expiring offline tokens?Shopify requires them for new apps. An expiring token stops working soon even if it leaks.
Will you put this in an email or a contract as a written commitment?A spoken assurance cannot be attached to a customer notice. A written sentence can.

The short note below is a template you can send. It is not a reply a vendor has already written to you.

Subject: Security information request, [store name]

Hello,

[App name] is installed on the Shopify store [store name]. 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 for the last 24 months, the Shopify scopes you request, the customer fields you store, how long you keep data after uninstall, and where tokens are held. We will keep the reply as a security commitment.

Thank you, [name, role]

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

A security review with Nodus Works

A store owner can work through this list alone. For a second pair of eyes, Nodus Works' Shopify technical support and maintenance audits installed apps, staff and collaborator accounts, custom app tokens 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.

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?

Whether or not it is mandatory, it should be on for every staff account. Swym also recommended two-factor authentication to merchants after the Wishlist Plus incident. Find the accounts where it is off in Settings, Users and permissions and turn it on.

Sources

Start your next project with Nodus Works

Scroll —