Stop a Credential Stuffing Attack: Ecommerce Login Fixes
Payments News

Muji, Chow Sang Sang, Sogo Breaches: Stop Credential Stuffing

Muji, Sogo and Chow Sang Sang show why a credential stuffing attack on ecommerce logins pays. Learn the warning signs and the defenses to turn on now.

Black combination padlock with its shackle open, resting on a silver laptop keyboard, suggesting unsecured logins

Photo: Pixabay

On this page 7 sections
  1. Muji, Sogo and Chow Sang Sang: What Each Disclosed
  2. How a Credential Stuffing Attack Hits an Ecommerce Store
  3. Why Loyalty Account Takeover Pays off for Attackers
  4. Read Your Login Data for the Warning Signs
  5. How to Stop Credential Stuffing Before the Holiday Rush
  6. When to Take Your Online Store Offline
  7. Account Takeover vs. Card Data Theft: What Changes for PCI and Chargebacks

Key takeaways

  • Credential stuffing can take over your customers' accounts without any break-in to your own systems, because passwords reused from other sites do the work.
  • Track your failed-login ratio as well as successful logins. In the illustrative example, successes rose about 21% while the failure rate jumped from 8% to about 94%.
  • Add step-up checks where money moves: points redemptions, email or address changes, and saved-card orders shipping to new addresses.
  • A takeover rarely exposes full card numbers, but the fraud chargebacks still land on you. Muji's case shows why you should delete stored card numbers you no longer need.

A credential stuffing attack on an ecommerce store works like this: criminals take email-and-password pairs leaked from other sites and try them on your login page by the thousands, betting that some of your customers reuse passwords. Each login that works hands over loyalty points, saved cards and shipping addresses. To stop it, make automated logins slow and costly, watch your failed-login ratio, and require a second check before anyone spends stored value or changes where an order ships.

This month's retail breaches in Asia show the pattern up close. Inside Retail Asia reported on Nov. 16, 2026 that Muji, Sogo and Chow Sang Sang each disclosed separate security incidents, and one of them involved credential stuffing aimed at an online store.

Muji, Sogo and Chow Sang Sang: What Each Disclosed

Muji (Ryohin Keikaku, Japan). The operator detected unauthorized access on Oct. 29 and believes up to about 27.26 million customer records may be affected, including registered users' email addresses, according to Jiji Press. The investigation later found card data too: about 1.09 million Muji Card records, including full card numbers, for members who joined between October 2000 and July 2021. On Nov. 12, Ryohin Keikaku said its failure to delete those numbers, which it had used to identify cardholders for rewards until July 2021, was a factor in the breach. Card issuer Credit Saison said it had not confirmed a rise in fraudulent use.

Sogo (Hong Kong). Hong Kong's privacy commissioner said on Nov. 12 that up to 820,000 loyalty members may be affected after unauthorized access to the department store's membership system, the South China Morning Post reported. The records include member numbers, names, phone numbers, email addresses and point balances.

Chow Sang Sang (Hong Kong). The jeweler first identified unauthorized access on Nov. 9, affecting its membership system and official e-commerce channels, with possible exposure of customer and employee data. It disclosed the incident on Nov. 12 and said it had contained the access, hired outside cybersecurity experts and reported the incident to police and the privacy regulator. The regulator was still verifying how many people were affected.

Read the dates closely. Inside Retail Asia reports that credential-stuffing attacks on an online store led to a temporary suspension starting Nov. 6, with the reopening pushed back so more security measures could go in. In the report, that detail follows Ryohin Keikaku's apology for an "additional unauthorised access incident." Chow Sang Sang says it first identified its own incident on Nov. 9, so the Nov. 6 shutdown appears to be Muji's store, not the jeweler's. As of Nov. 16, neither Sogo nor Chow Sang Sang had publicly named credential stuffing as a cause.

How a Credential Stuffing Attack Hits an Ecommerce Store

Credential stuffing doesn't require anyone to break into your systems. The attacker buys or downloads a list of email and password pairs stolen elsewhere, loads it into a bot, and fires the pairs at your login page or your app's login endpoint. Most attempts fail. The few that succeed belong to customers who used the same password with you as on the site that leaked.

That is why a breach in Tokyo or Hong Kong matters to a boutique in Ohio. Every large dump of email addresses becomes raw material for attacks elsewhere, and fields like phone numbers and point balances help criminals pick targets and write convincing phishing messages. Both Chow Sang Sang and Muji warned customers about impersonation scams.

Here is the part merchants miss. A stuffed login that succeeds looks like a real customer, with the right password and often a saved address and card. Checkout fraud screening can wave the order through because the account has years of good history. The evidence sits in your login logs, not your payment reports.

Why Loyalty Account Takeover Pays off for Attackers

Attackers want accounts that hold something they can spend or resell:

  • Loyalty points, which convert to merchandise or gift cards and get less scrutiny than card payments. Sogo's exposed records included point balances, a ready-made list of which accounts to hit first.
  • Saved cards. A stored card, usually kept as a token by your gateway, lets the attacker buy without ever knowing the card number.
  • Gift card and store-credit balances, which can be spent or moved within minutes.
  • Personal data and order history, useful for phishing and refund scams.

The damage looks different by vertical. A jeweler can lose a single high-ticket, easily resold order from one hijacked account, which is why high-value jewelry merchants should put the strongest checks on saved-card checkout. Apparel and boutique sellers tend to see many smaller orders and point redemptions that add up quietly. Retailers that tie in-store loyalty to an online account have one more exposure: points stolen online can be spent at a register, where nobody questions them.

Read Your Login Data for the Warning Signs

Ask your platform or developer for daily counts of login attempts, failures and successes, and watch for:

  • A jump in login attempts with no matching rise in site traffic, sales or email campaigns.
  • A failed-login ratio far above your normal level.
  • Many attempts against email addresses that were never customers, a sign the bot is working from someone else's list.
  • Attempts from many IP addresses, often proxies, with identical browser signatures.
  • Password resets, address changes, new saved cards or point redemptions right after login.

The worked example below uses illustrative numbers, not industry averages. Assume a store normally sees 3,000 login attempts a day and 8% fail, so 240 failures and 2,760 successes. One night, bots add 57,000 attempts on top of normal traffic, and assume 1% of them work. That is 570 hijacked accounts. Total attempts hit 60,000 and failures hit 56,670 (240 plus 56,430), so the failure rate jumps from 8% to about 94%. Successful logins only rise from 2,760 to 3,330, roughly 21%, which could pass for a busy promotion day. Watch successes alone and you miss the attack. Watch the failure ratio and it is obvious.

Carry it one step further. If attackers place orders with saved cards in 10% of those 570 accounts (57 orders) at an assumed $200 each, that is $11,400 in merchandise shipped. Each can come back as a fraud chargeback, plus your processor's dispute fee.

How to Stop Credential Stuffing Before the Holiday Rush

Most of these are settings, apps or plugins on Shopify, WooCommerce, BigCommerce and similar platforms, though availability varies by platform and plan.

  1. Put bot protection in front of every login-type page: sign-in, account creation, password reset and gift card balance lookup.
  2. Rate-limit by account and device as well as IP. Bots spread across thousands of IPs, so also cap attempts per account and slow responses after repeated failures.
  3. Offer multi-factor or passwordless login using one-time codes or passkeys, and require it for every staff and admin account with no exceptions.
  4. Check passwords against known-breached lists when customers create or change them, and force resets on accounts whose credentials turn up in a new dump.
  5. Add step-up checks where money moves. Require re-authentication before points redemptions, email or address changes, adding a card, or shipping a saved-card order to a new address. For card-not-present orders, 3-D Secure authentication brings the cardholder's bank into the decision.
  6. Use one generic error message ("email or password is incorrect") so bots can't confirm which emails have accounts.
  7. Email customers about every account change. The real owner often spots the change before the order ships.

If your online payment setup can't support step-up authentication or show you declines and disputes, fix that before December traffic peaks.

When to Take Your Online Store Offline

Shutting down costs sales, but sometimes it's the right call. Pull logins, or the whole storefront, when attacks continue after rate limits and bot protection are on, when you confirm takeovers that are turning into shipped orders, or when you suspect your own systems are compromised rather than just reused passwords hitting the front door. A middle path often works: turn off login and saved-card checkout, keep guest checkout running with full card entry, and freeze point redemptions until you've cleaned up.

Call your processor's risk team before the chargebacks arrive. Tell them what you saw, when it started, how many accounts were hit and whether card data could be involved. Merchant agreements commonly require prompt notice of a suspected card-data compromise, so read yours. Hold or cancel orders you believe are fraudulent. A refund issued before a dispute is filed is usually cheaper than fighting one later, as our guide on whether refunds return your processing fees explains.

For customers, force password resets, restore stolen points and explain plainly what happened. U.S. state breach-notification laws differ on what triggers a notice, and a takeover that exposes personal information may qualify. This is general information, not legal advice; confirm your obligations with a qualified attorney.

Account Takeover vs. Card Data Theft: What Changes for PCI and Chargebacks

Merchants often lump these together. In a typical account takeover, the attacker uses the customer's saved card through your checkout but never sees the full card number, because your gateway stores a token. That usually leaves it outside what counts as a card-data breach under PCI DSS, the card industry's security standard.

Muji shows how one becomes the other. Full card numbers kept long after the business stopped needing them turned an app breach into a card breach. PCI DSS expects merchants to keep stored card data to the minimum they need, so if any full card numbers sit in an old database, spreadsheet or order export, purge them and confirm the details with your processor.

Chargebacks follow the money, not the breach label. When a hijacked account buys with a saved card, the real cardholder disputes it as unauthorized. On card-not-present sales the merchant usually absorbs that loss unless liability shifted to the issuer, for example through an authenticated 3-D Secure transaction. Card network rules govern when that shift applies, so confirm specifics with your processor. The networks also monitor merchants with high fraud and dispute levels, and one bad week can push a small store into reserves or worse. Stolen points produce no chargeback at all; you simply eat the cost of the goods.

This week, pull 30 days of login data and write down your normal failed-login ratio, so a spike stands out the night it happens. Then make sure every staff and admin account requires a second factor, and review the staff-side defenses in our social engineering lessons for merchants. If you want a second look at your gateway, 3-D Secure settings or dispute history, you can request a free quote from MannyPay, and a specialist will respond within one business day.

Sources

  1. Data breaches hit Muji, Chow Sang Sang and Sogo (Inside Retail Asia, Nov. 16, 2026)
  2. 820,000 Sogo members at risk as department store, Chow Sang Sang hit by data breaches (South China Morning Post)
  3. 820,000 Sogo members at risk as department store, Chow Sang Sang hit by data breaches (The Star, Nov. 14, 2026)
  4. Muji Operator Fails to Delete Unnecessary Credit Card Data (Jiji Press via Nippon.com, Nov. 12, 2026)
  5. Credit card numbers of 1.09 million MUJI Card members leaked; breach follows earlier app leak (teiss)
  6. Chow Sang Sang reports breach of its membership system (Jing Daily, Nov. 16, 2026)

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading