Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 4 min read

Malwarebytes' Payment Vendor Was Hacked: Card Numbers and CVV Codes Copied, Buyers Told 16 Days Later. Who Handles Your Checkout?

Originally published at security.hackerme.ai. Nobody broke into Malwarebytes. They didn't have to. The company that runs part of its checkout did get breached, and that was enough to put some of its buyers' card numbers

Originally published at security.hackerme.ai.

Nobody broke into Malwarebytes. They didn't have to. The company that runs part of its checkout did get breached, and that was enough to put some of its buyers' card numbers and security codes in a stranger's hands.

The company is Cleverbridge. If you sell anything online through an outside payment provider, the Cleverbridge data breach is a good reason to spend ten minutes on one question: who actually stores your customers' cards?

What happened in the Cleverbridge data breach

Cleverbridge is an e-commerce platform that handles checkout, payments and subscriptions for software and SaaS companies. Buyers often see its name on the receipt instead of the brand they bought from.

On its own incident page, Cleverbridge says:

  • On 4 November 2026 it detected unauthorized activity on its platform and took affected systems offline.
  • All systems were back online the same day.
  • Its investigation later found that "a third party copied payment card data stored on our platform."
  • It began notifying affected people on 20 November, 16 days after detection.
  • It was not a ransomware attack. No systems were encrypted.

The public page does not list which card details were taken. But a notification shared with BleepingComputer does: the card number, the expiry date and the card security code (CVV/CVC). The same notice says no names, contact details or billing addresses were copied.

Cleverbridge has not said how the attackers got in, how long they were inside, or how many people were affected.

Who is affected

Cleverbridge lists many well-known software brands as customers, but it has not said which merchants' buyers were hit. One brand has confirmed it: on its support forum, Malwarebytes said Cleverbridge is one of its third-party payment processors and that "only a small subset" of its customers were affected.

If you bought software and saw Cleverbridge on your statement, watch for a notice by email. If you are a merchant that sells through Cleverbridge, your customers may be asking you about it right now.

Why the CVV part matters

Card industry rules (PCI DSS) say the security code must not be stored after a payment is authorized. That is the whole point of the code: a stolen card number alone is harder to use online. A number, expiry date and CVV together are what a criminal needs to buy things on most websites.

We don't know yet why the codes were retrievable. BleepingComputer asked Cleverbridge whether the card data was encrypted and why CVVs were accessible, and had no answer at the time of writing. Treat that as an open question, not a finding.

How stolen card data gets sold

In general, card data stolen in bulk ends up on carding markets on the dark web, where full card details (number, expiry, CVV) are sold in batches and tested with small purchases before bigger fraud. There is no public report that this specific data is for sale. But it is the reason banks often replace cards after a breach like this, and why breach-themed phishing usually follows. For a plain-English view of what monitoring can and cannot see, read what a dark web scan checks for your website.

What to check if you run a store or SaaS

You can't fix a vendor's servers. You can know which vendors hold your customers' data and what they keep.

  1. List every company that touches card data for you. Payment gateway, merchant of record, subscription billing, checkout plugins. Our post on the Rootways Magento skimmer shows how a single plugin can become the weak spot.
  2. Ask each one: do you store full card numbers? Is the CVV ever kept? How fast will you tell us about a breach, and in what format?
  3. Prefer tokenized payments. If your site never sees the card number, there is less to steal from you.
  4. Prepare your customer message. If a vendor is breached, your customers will hear your brand name, not theirs. The Shopify app breach that exposed customer addresses is another reminder that apps and vendors are part of your attack surface.
  5. Warn customers about phishing. Cleverbridge itself says it will never ask for card details or security codes by email, phone or text. Repeat that to your buyers.
  6. Check your own site, too. A vendor breach is out of your hands, but a skimmer or weak setting on your checkout page is not. A free website security scan shows what an attacker can see from the outside, and our guide on what your host handles and what you still need to check explains where your responsibility starts.

The bigger lesson

When a supplier is breached, the headline often still names the brand its customers know. (For another look at how an attack on a retailer lands on its customers, see the Container Store cyberattack.) Know your suppliers, ask the boring questions before something happens, and run a website vulnerability scanner on your own pages so the part you control is in good shape.

FAQ

Was Malwarebytes hacked?

No. Malwarebytes says this was a breach of Cleverbridge's systems, a payment processor it uses, and that only a small subset of its customers were affected.

What card data was stolen in the Cleverbridge breach?

Cleverbridge's public page says payment card data was copied. The notification seen by BleepingComputer lists card number, expiry date and CVV/CVC, and says names and billing details were not copied.

What should I do if I got a Cleverbridge notice?

Check your card statements, report charges you don't recognize to your bank, and consider asking for a new card. Don't click links in unexpected messages about the breach; go to the company's site or call the number on your card. Then check your website's security if you run an online store yourself.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.