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 online stores must check, and what NC breach law asks before Black Friday.

Man at a kitchen table holding a payment card up while looking at a laptop

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

That is not carelessness on your part. Between October 10 and October 20, 2026, attackers used three trusted Shopify apps to send shoppers who clicked Checkout to a lookalike payment page, take their card details, then forward them to the store's real checkout so the order still went through. If you run an online store in North Carolina, the code may have run on your product and cart pages without ever touching your theme files, and North Carolina's breach law may now ask you questions you cannot answer from your Shopify admin.

This is fixable, and most of the fix is 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 strip your app stack down before Black Friday on November 27 without losing the features that sell.

478
Apps that left the Shopify App Store between October 14 and 22, 2026, per 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, not the checkout itself.

How the fake checkout worked

The fake checkout worked by catching the Checkout button press on your storefront and sending the shopper somewhere else 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. The store saw a normal sale.

The script also fired only once per browser session, according to the same Merchant Fraud Journal report. A store owner testing their own checkout from a browser that had already seen the page would often get a clean result while new visitors hit the fake page.

The timeline, vendor by vendor

The 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, with code fixes completed at 16:32 UTC. Swym then reported a second wave from 21:17 UTC on October 18 that used the app's own Shopify access, 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 on your 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 lands in the worst possible month. The holiday rush is weeks away, your app stack is at its fullest, and North Carolina's Identity Theft Protection Act treats a credit or debit card number as personal information. If any of your shoppers typed a card into the fake page, you may be holding a breach question you did not cause and cannot see in your data.

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

The real cost of this attack is not the code. The cost is that every normal signal you rely on said everything was fine. These are the six problems store owners are dealing with now.

1. Your orders cannot tell you whether you were hit

Your order data cannot show a hijack, because every hijacked shopper was forwarded to your 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. That puts you in the position of learning about a security incident from your customers, which is the slowest and most expensive way to learn it.

2. A clean theme search proves very little

A theme code search 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 were 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 your theme. It only existed in your shopper's browser.

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

North Carolina's notice rule bites earlier than most stores 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, and must also report the breach to the Attorney General's Consumer Protection Division. There is no minimum number of affected residents for that Attorney General report. 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 gives injured residents a private right of action under its breach law, according to a May 2026 comparison of Southeast breach laws. That changes the arithmetic for a North Carolina store. A slow or vague response is not only a regulator risk. A shopper who lost money and heard nothing from you has a direct route 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 they paid twice in effect: once to the attacker, once to you. Your sale is real. Their loss is real too. Do not assume a completed order means a safe shopper.

5. Paused apps break the features that sell

Paused apps keep their buttons on your store but stop doing the work. Swym's FAQ says Wishlist Plus icons, buttons and embeds may still show while the app is paused, but they do not work, and wishlist and alert emails stopped because they depend on Swym's connection to your store. For a store that relies on back-in-stock alerts and saved-item reminders in November, that is a dead button on every product page and a silent gap in your email revenue.

6. Nobody has said who pays for the fraud

The question of who absorbs the cost is still open. Merchant Fraud Journal asks it directly: who absorbs chargebacks and fraud losses when a breach traces back to a vendor's app? Your payment processor may see disputes from affected cards. Your app vendor's terms may limit its liability. Until someone answers, the cost of the investigation, the customer service time and any disputes sits with you.

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

The three states treat the same attack in noticeably different ways. Florida has the hardest clock, North Carolina has the lowest trigger for telling the Attorney General, and Georgia's statute is the narrowest of the three. A store that sells into all three should plan to the strictest rule in each column.

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

North Carolina is the strictest of the three on who must hear about a breach. The state's Department of Justice says more than 20,000 security breaches have been reported to it since December 2005. Its definition of a security breach is 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 itself is based.

For a store owner in Charlotte, Raleigh or Durham, the practical question is ownership. The fake page sat on an attacker's domain, not your system. Whether a card typed into that page counts as a breach of data you "own or license" is a question for your lawyer, and the answer depends on facts only your app vendor can give you: which hours the code ran on your store and on which pages. Get that answer in writing from the vendor before you decide. 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 do a large share of the year's revenue between Thanksgiving and Christmas. Our North Carolina market page covers how stores there compete for that window. A breach notice sent in the first week of December lands at the moment your shoppers are deciding where to buy.

StateDeadline to notify shoppersRegulator noticeCredit bureau noticeMain enforcement risk
North CarolinaWithout unreasonable delayAttorney General's Consumer Protection Division, no minimum countMore than 1,000 people notifiedAttorney General action and a private right of action
FloridaNo later than 30 days, 15 more with good causeDepartment of Legal Affairs if 500 or more Floridians affectedMore than 1,000 people notifiedCivil penalty of up to $500,000 for late notice
GeorgiaMost expedient time possible, without unreasonable delayNone in the statuteMore than 10,000 residents notifiedFair Business Practices Act enforcement

Florida and Georgia: a hard clock and a narrow statute

Florida runs on a fixed 30-day clock. 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, and must 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. Missing the 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 you, which the statute calls third-party agents, 10 days to tell you about a breach on their side. A Miami or Orlando store should hold its app vendors to that.

Georgia's breach statute is the narrowest of the three. The Sentra comparison says 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 only requires notice to the credit bureaus when more than 10,000 Georgia residents are notified. Violations are treated as unlawful practices under Georgia's Fair Business Practices Act, which the Georgia Attorney General enforces. An Atlanta or Savannah store should not read the narrow statute as a reason to stay quiet: if Florida or North Carolina shoppers were hit in the same window, those states' rules apply to them regardless of where you are.

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

Every app that loads code on your storefront is code someone else can change. That is the lesson of October 2026, and it turns your app list from a features question into a risk question. Most stores never priced that risk because nothing forced them to.

Apps you forgot you installed still run

Old apps keep running long after you stop 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 your theme. A store that has tried five upsell apps over three years may still be loading code from two of them. Each one is a vendor whose servers, staff accounts and internal tools now sit inside your checkout path.

Shopify is closing one door, not all of them

Shopify is already narrowing how apps load code, but the change does not close 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. The replacement is the app embed block, which you can see and switch off in the theme editor. That gives you visibility. It does not stop an embed from fetching new code from its vendor's servers on every page load.

The holiday math makes every lost checkout expensive

The holiday season makes a broken or distrusted checkout unusually expensive. 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, which is exactly why a lookalike checkout works best on the device that carries most of your 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 the moment the checkout page loads. Shopify's checkout runs on your own domain or your myshopify.com address. Any other domain at that point is an incident. Repeat it from the cart drawer and on a phone.

What works: a checkout path you can actually vouch for

What works is treating the path from product page to checkout as a short, owned, tested route, with as few outside parties on it as possible. You cannot audit a vendor's servers. You can decide how many vendors get to run code before the Checkout button.

Cut the apps that touch the cart and product pages

The most effective fix is 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 your theme editor, ask what each one earns, and remove the ones that do not pay for their place. Product options, gift notes, simple bundles and cart upsells can often be built into your theme with Shopify's own features, where a change shows up in your code history instead of arriving silently from a vendor's server.

Turn off custom code fields you do not use

Custom JavaScript and custom HTML settings inside apps are where the first wave hid. 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 recognise everything in it, clear it and ask the vendor why it was there.

Test like a stranger, on a schedule

Testing only works if you test the way a new shopper arrives. Because the script fired once per session, you need a fresh private window every time, on desktop and on a phone, from both the cart page and the cart drawer. Do it 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 as ones to search for in your theme files and 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 your payment processor and which lawyer reads 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, so the features that lift conversion stay and the third-party code that adds risk goes. The work sits in our Website Design and Revamp service and our e-commerce marketing practice.

A checkout path audit

We start with what a new shopper actually experiences. 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: keep, rebuild natively, or remove, with the conversion role of each app stated next to its risk.

Native rebuilds for the features that sell

Where an app does a job your theme can do, we rebuild it 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 your conversion rate does not pay for the security fix.

A holiday-ready incident checklist

We hand over a short incident checklist for your team: who to call, what evidence to capture, what to ask your 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 marks which state's clock starts first so nobody has to work it out under pressure.

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

You know the fix worked when your checkout path is shorter, your tests stay clean, and your conversion rate holds. These four numbers tell you.

Outside domains before checkout

Count the outside domains your product and cart pages contact, and the number of vendors behind them. Good looks like a short list where you can name the owner and the purpose of every entry. Any domain nobody on your team can explain is a finding, not a detail.

Clean fresh-session tests

Track how many fresh-session checkout tests you ran each week and how many reached your own domain first time. Good looks like 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. Good looks like a flat or rising rate. A drop after a removal tells you the app was earning its place and needs a native rebuild rather than deletion.

Time to vendor answer

Measure how long each app vendor takes to tell you, in writing, whether its code ran on your store and when. Good looks like days, not weeks. A vendor that cannot answer in a week is a vendor you should plan to replace 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 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 Department of Legal Affairs must also be told within 30 days. Late notice can cost up to $500,000 in civil penalties.

Remove the 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.

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