Shopify Store Hacked? Secure Staff, Apps and Theme Code

unflagdomain Team·UPDATED November 13, 2026

A hacked Shopify store is almost never about infected server files. Shopify runs the platform, so the realistic attacks are a taken-over staff account, a connected app going rogue, or code added to your theme. Clean up that layer first, then ask the security vendors showing the warning to re-check the domain.

TL;DR: Your Shopify store has no server files you own and no PHP to patch — the platform is hosted, so a "hacked" store is usually an access problem, a bad app, or injected theme code. A browser or antivirus warning is a security vendor's blocklist entry, not a Shopify verdict. Fix the access first; chase the flags after.

This is the incident guide for a store you think someone got into: what to check, in order. If the store is blocked or flagged and nothing points to a break-in, start with the blocked-store emergency guide instead; it covers the triage for every platform.

Can a Shopify store even be hacked?

Yes — but not the self-hosted way the WordPress guides describe. On a self-hosted store you own the server: attackers get in through a vulnerable plugin, an uploaded file, or a backdoored theme. On Shopify the server half of that does not exist on your side. Shopify hosts the store — every store starts on a myshopify.com address and serves customers from the custom domain you connect (Shopify Help Center) — and there is no PHP and there are no server files you manage; what can be changed is apps, staff accounts and theme code.

What remains is the account layer, and that is where attacks land:

  • Staff accounts and permissions. Store access is user accounts with roles — "Create and assign roles to each user with the permissions that they need to complete tasks" (Shopify Help Center). Every admin login is a door; every unused one is a door nobody is watching.
  • Connected apps. Third-party apps run with the access you grant them, and most apps are built by third-party developers, not by Shopify (Shopify Help Center).
  • Theme code. Your theme is the one place code genuinely lives on your side of Shopify.
  • The domain itself. The name customers type can be flagged by a security vendor with nothing on the store having changed.

And one more option worth holding open: nothing may have been hacked at all — see the false-positive section below.

What the warning actually is — and who is showing it

Warnings that feel identical come from different places, and where you see it tells you who owns the fix.

  • A notice inside your Shopify admin comes from Shopify itself. If the platform is reporting something about your account, Shopify Support is the right door.
  • A red full-page browser screen, or an antivirus popup, comes from a security vendor's blocklist — Google Safe Browsing behind Chrome and Safari warnings, or an antivirus's URL reputation engine. Only the vendor that published the list can change it.

Read the exact wording and address in the warning. Vendors flag the hostname they checked, and shoppers reach your store on the custom domain you connected — that is the address that lands in lists; the free myshopify.com address is a separate host with a separate entry. A warning is a vendor's classification of that hostname, not a verdict Shopify handed down, and Shopify can't overturn it for you.

You don't have to guess which vendors are acting on what: run the domain through a free multi-vendor scan and see which lists carry it.

First: check your staff accounts and apps

Open your Shopify admin's user settings (Settings > Users, Help Center) and review everyone who can get in. Shopify's own post-incident checklist is plain about it: "Review and update your staff or collaborator accounts and their permissions", especially for staff with sensitive permissions (Shopify Help Center).

  • Look for accounts you don't recognize, invitations you didn't send, and collaborator accounts you can't place.
  • Cut each role back to the job that person does — an order-desk login doesn't need theme access.
  • Remove anyone who shouldn't be there. A former employee's live login is a classic way in.

Then check what the store recorded: Settings > General, and under Resources open the Store activity log. It shows recent actions by people, apps and channels, and it's where suspicious patterns surface — "Changes at unusual times when no one should be working", "Actions from unfamiliar users or apps", "Unexpected staff deletions or permission changes" (Shopify Help Center). It's view-only and covers only recent activity, so read it now rather than later.

Apps next: Settings > Apps. Every installed app holds permissions you granted it, possibly years ago. Uninstall what you no longer use — but export anything you need first, because "Some apps store data that you can't recover after uninstalling" (Shopify Help Center).

Second: check your theme and third-party scripts

The theme is where code actually lives on a Shopify store, which makes it the one place worth reading after a scare. Duplicate the theme first, so you keep a copy of what was there. Then go to Online Store, click the three-dot menu, then Edit code (Shopify Help Center). Look for:

  • Script tags pulling JavaScript from domains you don't recognize.
  • Snippets that are obfuscated or oddly minified compared with the rest of the theme.
  • Code left behind by an app you removed — Shopify's uninstall help notes some apps add theme code that isn't removed automatically, so an app can be gone while its code still runs.

Apps don't only touch the theme: embeds and tracking pixels can load through the storefront and checkout, so reviewing an app's permissions means reviewing code that runs under your store's name.

If one file was modified, its Timeline view can compare versions and restore it — but it restores one file at a time, can't restore a whole theme or recover deleted files, and keeps no history for images and other assets (Shopify Help Center). If the theme has more changes than you can account for, replace it with a fresh copy and reapply your settings.

For how this class of attack works — a script you trusted turning malicious, your domain carrying the flag — read our guide to third-party scripts getting a site blacklisted. The supply-chain mechanism is theirs; the takeaway for a Shopify store: the flag lands on the domain that served the code, whoever wrote it.

Third: clean up and lock down

If you think the account itself was accessed, Shopify's guidance starts with support: "If you think your account has been hacked or compromised, then contact Shopify Support immediately" (Shopify Help Center). Then work in this order:

  • Change the password on the email account behind your store, then the Shopify account password. If the reset email never arrives, contact support — that silence is itself a signal.
  • Turn on two-step authentication. One Shopify-specific wrinkle: staff set it up on their own accounts, and "the store owner can't activate two-step authentication for any other staff member" (Shopify Help Center). Make it a condition of access.
  • If two-step authentication was bypassed, remove the authentication method for the compromised device and set it up again on a different device.
  • Check for suspicious login activity, then redo the staff, apps and activity-log pass above.

One warning for the cleanup window: scammers send fake "your store is compromised" emails precisely when owners are primed to act. Shopify only sends mail from @shopify.com, @email.shopify.com, @em.shopify.com and @shopify-billpay.melio.com — anything from a free webmail address claiming to be Shopify is not (Shopify Help Center). Don't sign in through a link in any email; open your admin yourself. If you already clicked or entered credentials: change your password, activate two-step authentication, contact support, and report the attempt to phishing@shopify.com.

When it is a false positive

A clean store can still be flagged. A store can be flagged for reasons that are not on the store itself, such as the reputation of a newly registered domain.

Before you conclude "false positive", run two checks: the access review above (a real takeover leaves traces in the user list and activity log), and a test of your store from a different network in an incognito window. Then remember there is no appeal button in your admin — the vendor's own review channel is the only lever.

A clean store plus a persistent flag is exactly what a vendor re-check is for.

Still flagged after cleanup? The removal requests

Once the account is locked down, nothing on the store is unexplained and a vendor still flags the domain, the removal service is a one-time €49 per domain; see the pricing page for the rest. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard.

Keeping the store out of trouble

Most repeat incidents reuse the same few doors:

  • Least privilege for staff — roles per person, reviewed on a schedule, removed the day someone leaves.
  • App hygiene — uninstall what you don't use, then check the theme for code the app left behind.
  • Two-step authentication, verified per person — you can't switch it on for staff, so check on onboarding.
  • Protect the owner email — it is the reset path to everything. Give it its own strong password and second factor.
  • Watch reputation, not just uptime — the free checker shows what outside systems say before a customer does.

Start with the facts: run the free scan to see which vendors currently flag the domain, work the access checklist, and request reviews only once the store is genuinely clean. If you'd rather not handle the correspondence yourself, the removal service exists for exactly that stage — after the cleanup, never instead of it.

// FAQ
  • Not the way a self-hosted store can — Shopify runs the servers, so there are no site files to infect. Attacks happen at the account layer instead: staff logins taken over, connected apps pulling in compromised scripts, or malicious code added to the theme. A warning on your domain can also be a false positive on a store that was never touched.

  • Look at where the warning appears. Notices in your Shopify admin come from Shopify itself; a red browser page or an antivirus popup comes from a security vendor's blocklist, and only that vendor can change it. A multi-vendor scan shows which lists currently carry your domain.

  • The scan shows which security vendors flag the domain; each has its own report channel, and none of them share one. Request a re-check from each vendor that lists you, and keep the reports factual: what the store is, and that it carries nothing malicious.

  • No. We do not clean malware or recover accounts — you secure the account and clean the code first; we trust your description. The one-time €49 covers the removal requests. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard.

  • No one can promise a date — each vendor reviews on its own schedule. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). From there the vendor's queue decides.