Skip to main content

Three Shopify apps sent shoppers to fake checkouts. Here is what a North Carolina store should check before Black Friday.

Three Shopify apps sent shoppers to fake checkouts in October 2026. What North Carolina stores must check, and what NC breach law asks before Black Friday.

Open empty cardboard shipping box with its flaps up on a light surface

The Short Version

Between October 10 and October 20, 2026, attackers used three Shopify apps to send shoppers to a lookalike payment page that took card details, then forwarded them to the real checkout. North Carolina stores should test checkout in a fresh private browser window and read the address bar. Remove apps that do not earn their place.

Your orders look normal, and your checkout test came back clean. Then a customer emails to say their card was used somewhere strange two days after they bought from you, and they insist the payment page "looked a bit off". You check Shopify and your theme and find nothing.

The store owner did nothing careless here. Between October 10 and October 20, 2026, attackers used three trusted Shopify apps to send shoppers who clicked Checkout to a lookalike payment page, collect their card details, and then forward them to the store's real checkout so the order still went through. For an online store in North Carolina, the code may have run on product and cart pages without touching the theme files, and North Carolina's breach law may now raise questions the Shopify admin cannot answer.

Shopify store owners can fix most of this with a one-afternoon audit. This article sets out what happened, why a clean theme search proves little, what the North Carolina, Florida and Georgia breach notice rules mean for a store that cannot tell whether it was hit, and how to cut down an app stack before Black Friday on November 27 while keeping the features that sell.

478
Apps removed from the Shopify App Store between October 14 and 22, 2026, according to one tracker
3
App vendors that confirmed attackers used their apps to hijack checkout clicks
20,000+
Security breaches reported to the North Carolina Attorney General since December 2005
$275.1B
US online holiday sales Adobe projects for November and December 2026

What changed: trusted Shopify apps became a route to fake checkouts

Three Shopify app vendors have confirmed that an unauthorized party used their apps to redirect shoppers to fake payment pages in October 2026. Merchant Fraud Journal reported on October 26 that the affected apps are Selleasy by Logbase, Swym Wishlist Plus by Swym, and Hulk Product Options by HulkApps. No source says Shopify's own checkout or systems were breached. The attackers hijacked the click that leads to checkout, and Shopify's checkout itself stayed intact.

How the fake checkout worked

The fake checkout intercepted the Checkout button press on a Shopify storefront and sent the shopper to another page first. A German developer, Roman Zipp, found the campaign on October 10, 2026 while buying from a Shopify store. The Checkout button sent him to a lookalike page on a domain called biliing[.]top, which asked for payment and personal details and then forwarded him to the genuine checkout. The order completed, and the store recorded a normal sale.

The malicious script fired only once per browser session, according to the same Merchant Fraud Journal report. A store owner testing checkout from a browser that had already loaded the page would often see a clean result, while new visitors reached the fake page.

The timeline, vendor by vendor

The three incidents ran in overlapping windows across eleven days. Selleasy's malicious script ran from 07:47 to 15:00 UTC on October 13. Swym's incident FAQ, dated October 20, says an unauthorized change to its Wishlist Plus configuration loaded a script on a subset of storefronts between 10:06 and 11:56 UTC on October 14, and code fixes were completed at 16:32 UTC. Swym then reported a second wave, starting at 21:17 UTC on October 18, that used the app's own Shopify access. Swym paused the app for every merchant and revoked its Shopify credentials.

Shopify's App Store listed all three apps as unavailable from October 15. Delisting blocks new installs, but an app already installed on a store keeps running. Revenue Shield, a vendor that sells checkout monitoring, counted 478 apps removed from the App Store between October 14 and 22, with 305 removed on October 20 alone. Shopify has not confirmed that count or explained most of the removals.

What it means for a North Carolina store

For a North Carolina online store, the attack arrived in the worst possible month. The holiday rush is weeks away, app stacks are at their fullest, and North Carolina's Identity Theft Protection Act treats a credit or debit card number as personal information. If any shoppers typed a card into the fake page, the store may face a breach question it did not cause and cannot see in its own data.

The pain points: what this does to your store this quarter

The biggest cost of the Shopify checkout hijack is that every normal signal a store owner relies on said everything was fine. Store owners are dealing with six problems now.

1. Your orders cannot tell you whether you were hit

Shopify order data cannot reveal a hijack, because every hijacked shopper was forwarded to the store's real checkout and paid there. Revenue, conversion rate and average order value all look healthy. The first sign is usually a customer email about a strange payment page, or a fraud report on a card weeks after the order. The store owner then learns about a security incident from customers, the slowest and most expensive way to find out.

2. A clean theme search proves very little

A search of theme code would have missed the first wave entirely. Fudge's technical write-up of the attack explains that many storefront apps fetch their settings from the vendor's servers on every page load, and in the first wave those settings carried the payload. In the HulkApps case, the app's own file on Shopify's CDN was clean, while about 22.7 KB of extra JavaScript sat in a custom code field served from the vendor's API. The code never existed in the store's theme, only in each shopper's browser.

3. North Carolina asks for an Attorney General notice with no headcount floor

North Carolina's breach notice rule applies earlier than most store owners expect. The North Carolina Department of Justice's breach guidance says any business that owns or licenses personal information of North Carolina residents and suffers a security breach must notify the affected people without unreasonable delay. The business must also report the breach to the Attorney General's Consumer Protection Division, and that report has no minimum number of affected residents. A Charlotte or Raleigh store with a handful of exposed shoppers faces the same question as a large retailer.

4. North Carolina shoppers can sue

North Carolina's breach law gives injured residents a private right of action, according to a May 2026 comparison of Southeast breach laws. That raises the stakes for a North Carolina store, because a slow or vague response creates risk with shoppers as well as regulators. A shopper who lost money and heard nothing from the store can go straight to court, and a public complaint during the holiday season costs more in lost trust than any notice letter costs to send.

The quiet trap: the fake page took card details and then sent shoppers to your real checkout, so in effect they paid twice, once to the attacker and once to you. Your sale is real, and so is their loss. A completed order does not mean the shopper is safe.

5. Paused apps break the features that sell

A paused Shopify app keeps its buttons on the store but stops doing the work. Swym's FAQ says Wishlist Plus icons, buttons and embeds may still appear while the app is paused but do not function, and wishlist and alert emails stopped because they depend on Swym's connection to the store. For a store that relies on back-in-stock alerts and saved-item reminders in November, the pause means a dead button on every product page and missing email revenue that no alert will flag.

6. Nobody has said who pays for the fraud

Nobody has yet settled who absorbs the cost of the Shopify app breach. Merchant Fraud Journal asks the question directly: who absorbs chargebacks and fraud losses when a breach traces back to a vendor's app? The store's payment processor may see disputes from affected cards, and the app vendor's terms may limit its liability. Until someone answers, the store carries the cost of the investigation, the customer service time and any disputes.

By market: how North Carolina, Florida and Georgia treat a fake checkout

North Carolina, Florida and Georgia treat the same fake checkout attack differently. Florida has the strictest deadline, North Carolina has the lowest threshold for telling the Attorney General, and Georgia's statute is the narrowest of the three. A store selling into all three states should follow the strictest rule in each column of the table below.

North Carolina: report to the Attorney General, whatever the count

Of the three states, North Carolina is strictest about who must be told of a breach. The state's Department of Justice says more than 20,000 security breaches have been reported to it since December 2005. North Carolina defines a security breach as unauthorized access to or acquisition of unencrypted records containing personal information, where illegal use has occurred, is reasonably likely, or creates a material risk of harm. Personal information includes a credit or debit card number, and the law covers any business that owns or licenses the personal information of North Carolina residents, wherever the store is based.

For a store owner in Charlotte, Raleigh or Durham, the practical question is ownership of the data. The fake page sat on an attacker's domain outside the store's systems. Whether a card typed into that page counts as a breach of data the store "owns or licenses" is a question for a lawyer, and the answer depends on facts only the app vendor can supply: the hours the code ran on the store and the pages it ran on. Get that answer from the vendor in writing before deciding. North Carolina also expects notice to the consumer reporting agencies when more than 1,000 people are notified, according to the Sentra comparison.

The North Carolina market adds its own timing pressure. Stores in the Triangle and around Charlotte that sell gifts, apparel and home goods earn a large share of the year's revenue between Thanksgiving and Christmas, and our North Carolina market page covers how they compete for that window. A breach notice sent in the first week of December reaches shoppers just as they are deciding where to buy.

StateDeadline to notify shoppersRegulator noticeCredit bureau noticeMain enforcement risk
North CarolinaWithout unreasonable delayAttorney General's Consumer Protection Division, with no minimum countRequired when more than 1,000 people are notifiedAttorney General action and a private right of action
FloridaNo later than 30 days, plus 15 more with good causeDepartment of Legal Affairs if 500 or more Floridians are affectedRequired when more than 1,000 people are notifiedCivil penalty of up to $500,000 for late notice
GeorgiaIn the most expedient time possible, without unreasonable delayNone required by the statuteRequired when more than 10,000 residents are notifiedEnforcement under the Fair Business Practices Act

Florida and Georgia: a hard clock and a narrow statute

Florida gives a store a fixed 30-day deadline. Under section 501.171 of the Florida Statutes, a covered entity must notify each affected Floridian no later than 30 days after it determines a breach occurred or has reason to believe one did. It must also notify the Department of Legal Affairs within the same 30 days if 500 or more Floridians are affected. Personal information includes a card number combined with any required security code, which is exactly what a fake payment page collects. A missed deadline costs $1,000 a day for the first 30 days, then $50,000 for each 30-day period up to 180 days, capped at $500,000. Florida also gives vendors that process data for a business, which the statute calls third-party agents, 10 days to report a breach on their side, and a Miami or Orlando store should hold its app vendors to that.

Georgia's breach statute is the narrowest of the three. According to the Sentra comparison, section 10-1-912 of the Georgia Code requires notice in the most expedient time possible and without unreasonable delay, requires no notice to the Attorney General, and requires notice to the credit bureaus only when more than 10,000 Georgia residents are notified. Violations count as unlawful practices under Georgia's Fair Business Practices Act, which the Georgia Attorney General enforces. An Atlanta or Savannah store should still respond fully: if Florida or North Carolina shoppers were hit in the same window, those states' rules apply to them wherever the store is located.

Hidden costs: why your app stack is now a liability line

Any Shopify app that loads code on a storefront runs code its vendor can change at any time. After October 2026, the app list is a security risk to manage as well as a set of features. Most stores never priced that risk because nothing forced them to.

Apps you forgot you installed still run

Old Shopify apps can keep running long after the store owner stops thinking about them. Fudge's guide points out that app embeds are injected near the closing head or body tag of every page, and that uninstalling an app does not always remove everything it added to the theme. A store that has tried five upsell apps over three years may still load code from two of them. Each of those vendors has servers, staff accounts and internal tools that now sit inside the store's checkout path.

Shopify is closing one door, not all of them

Shopify is already narrowing how apps load code, but the change leaves open the route this attack used. The Shopify developer changelog says that from October 1, 2026 apps can no longer create or update storefront script tags, and that on March 1, 2027 Shopify will stop injecting script tags into storefronts. Script tags are being replaced by app embed blocks, which store owners can see and switch off in the theme editor. Embed blocks improve visibility, but an embed can still fetch new code from its vendor's servers on every page load.

The holiday math makes every lost checkout expensive

A broken or distrusted checkout costs far more during the holiday season. Adobe projects US online sales of $275.1 billion for November and December 2026, up 6.7% on last year, with $47.5 billion of that in the five days from Thanksgiving through Cyber Monday. Adobe expects 57.4% of holiday online sales to come from mobile devices. A shopper on a phone sees less of the address bar than a shopper on a laptop, so a lookalike checkout works best on the device that brings in most of the revenue.

Check this today: open a private browser window, add a product to the cart, press your standard Checkout button and read the address bar as soon as the checkout page loads. Shopify's checkout runs on your own domain or your myshopify.com address, so any other domain at that point means an incident. Repeat the test from the cart drawer and on a phone.

What works: a checkout path you can actually vouch for

A Shopify store protects its checkout by treating the path from product page to checkout as a short, tested route it controls, with as few outside parties on it as possible. A store owner cannot audit a vendor's servers but can decide how many vendors run code before the Checkout button.

Cut the apps that touch the cart and product pages

The most effective fix is running fewer storefront apps on the pages that lead to checkout. Swym's FAQ says the malicious script ran mainly on collection, product and cart pages and attached itself to the checkout button. List every app embed switched on in the theme editor, ask what each one earns, and remove those that do not pay for their place. Product options, gift notes, simple bundles and cart upsells can often be built into the theme with Shopify's own features, where any change shows up in the code history and nothing can arrive unseen from a vendor's server.

Turn off custom code fields you do not use

The first wave of the attack hid in custom JavaScript and custom HTML settings inside apps. Fudge reports that the HulkApps payload sat in a custom code field, that Selleasy locked its custom JS setting after the attack, and that an earlier July 2026 case at Qikify used HTML fields in app settings. Open every app that offers such a field. If you do not recognize everything in it, clear the field and ask the vendor why the code was there.

Test like a stranger, on a schedule

A checkout test only catches this attack if it mimics a new shopper. Because the script fired once per session, each test needs a fresh private window, on desktop and on a phone, from both the cart page and the cart drawer. Run the test weekly through the holidays and after every app update. Swym also lists the domains checkout-guard[.]top, account-confirm[.]top, billing-confirm[.]top and checkout-secure[.]top to search for in theme files and to block.

Write the incident plan before you need it

An incident plan written now is worth more than a perfect one written during a crisis. Decide who calls the app vendor, who contacts Shopify Support, who speaks to the payment processor, and which lawyer checks the North Carolina, Florida and Georgia rules against your facts. Keep a one-paragraph customer message ready. Shoppers forgive an honest, fast notice far more readily than a store that went quiet.

How Leadnox helps online stores lock down checkout

Leadnox audits and rebuilds the path from product page to checkout for online stores, keeping the features that lift conversion and removing the third-party code that adds risk. The work is part of our Website Design and Revamp service and our e-commerce marketing practice.

A checkout path audit

We start with what a new shopper actually sees. We run fresh-session checkout tests on desktop and mobile, list every outside domain your product and cart pages contact, map each app embed to the vendor behind it, and flag any custom code field we cannot account for. You get a plain list marking each app keep, rebuild natively, or remove, with its role in conversion stated next to its risk.

Native rebuilds for the features that sell

When an app does a job your theme can do, we rebuild that feature in the theme so it changes only when someone edits it. Product options, gift messages, simple bundles and cart upsells are the usual candidates. We test every rebuild against the old version before the app comes out, so the security fix does not cost you conversion rate.

A holiday-ready incident checklist

We give your team a short incident checklist covering who to call, what evidence to capture, what to ask app vendors in writing, and a draft customer message for your lawyer to approve. For stores selling into North Carolina, Florida and Georgia, the checklist shows which state's deadline starts first, so nobody has to work it out under pressure.

Measuring: how you know your checkout is clean and still converting

A Shopify store's checkout fix is working when the checkout path is shorter, tests stay clean and conversion rate holds. Four numbers show it.

Outside domains before checkout

Count the outside domains your product and cart pages contact, and the vendors behind them. A healthy result is a short list where you can name the owner and purpose of every entry. Treat any domain nobody on your team can explain as a security finding.

Clean fresh-session tests

Track how many fresh-session checkout tests you ran each week and how many reached your own domain on the first try. The target is 100% clean across desktop, mobile, cart page and cart drawer, with a test logged after every app update.

Checkout conversion after app removals

Watch the share of sessions that reach checkout and complete it, before and after each app removal or rebuild. A flat or rising rate is healthy. A drop after a removal shows the app was earning its place and should be rebuilt natively instead of deleted.

Time to vendor answer

Measure how long each app vendor takes to confirm in writing whether its code ran on your store, and when. Days is a healthy answer and weeks is not. Plan to replace any vendor that cannot answer within a week before the next incident.

Frequently Asked Questions

No public source says Shopify's own checkout or systems were breached. Attackers used three third-party apps, Selleasy, Swym Wishlist Plus and Hulk Product Options, to load code on store pages that sent shoppers who clicked Checkout to a lookalike payment page. That page took card details and then forwarded shoppers to the store's real checkout, so orders still completed.

Open a fresh private browser window, add a product to the cart, press the standard Checkout button and read the address bar as the checkout loads. It should show your own domain or your myshopify.com address. Repeat the test from the cart drawer and on a phone, then search your theme files for checkout-guard and the other domains Swym has listed.

Yes, if a security breach of personal information occurred. North Carolina requires a business that owns or licenses North Carolina residents' personal information to notify affected people without unreasonable delay and report the breach to the Attorney General's Consumer Protection Division, with no minimum number of affected residents. Whether a fake checkout page counts as your breach is a question for your lawyer.

Florida allows no more than 30 days after a store determines a breach occurred or has reason to believe one did, with 15 more days possible for good cause. If 500 or more Floridians are affected, the store must also notify the Department of Legal Affairs within 30 days. Late notice can cost up to $500,000 in civil penalties.

Remove the Shopify apps that do not earn their place, especially on product and cart pages, and keep the ones that clearly lift sales. Rebuild simple features such as product options, gift notes and cart upsells in your theme where you can. Test checkout in a fresh private window after every change, and finish before Black Friday on November 27.

Sources

  1. Merchant Fraud Journal reported on October 26. merchantfraudjournal.com
  2. Swym's incident FAQ, dated October 20. getswym.com
  3. Fudge's technical write-up of the attack. fudge.ai
  4. North Carolina Department of Justice's breach guidance. ncdoj.gov
  5. May 2026 comparison of Southeast breach laws. sentra.io
  6. Section 501.171 of the Florida Statutes. leg.state.fl.us
  7. Shopify developer changelog. shopify.dev
  8. Adobe projects. digitalcommerce360.com

Drafted with AI assistance from the public sources listed above. How we write. This article is general information for business owners, not legal, tax, medical or financial advice. Rules change and differ by state, so check the source documents or ask a qualified professional before you act on it.

Not sure what runs between your product page and checkout?

Leadnox audits the checkout path for online stores in North Carolina, Florida and Georgia, removes the third-party code you do not need and rebuilds the features that sell, so Black Friday traffic reaches a checkout you can vouch for. Start with a free checkout audit.

Get My Free Checkout Audit