Loading SecureCyberVM…
SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

Cleverbridge breach: hackers copied card numbers and CVV codes from payment platform

E-commerce platform Cleverbridge says attackers copied stored payment card data after a November 4 intrusion. Notifications list card numbers, expiry dates and CVV/CVC codes; the number of affected buyers has not been disclosed.

Cleverbridge breach: hackers copied card numbers and CVV codes from payment platform

Cleverbridge, an e-commerce and subscription billing platform used by software and SaaS vendors, has disclosed a breach in which an unauthorized third party copied payment card data stored on its platform. According to a customer notification reviewed by BleepingComputer, the stolen details include card numbers, expiration dates and CVV/CVC security codes.

The company has not said how many buyers were affected, which merchants’ customers were involved, or how the attackers got in. Malwarebytes has confirmed that Cleverbridge is one of its payment processors and that a small subset of its customers were affected, according to a report published by security.hackerme.ai.

What happened

According to Cleverbridge’s incident disclosure, as reported by BleepingComputer, the company detected unauthorized activity on November 4, 2026, and temporarily took systems offline to contain it. Systems were brought back online the same day, but the subsequent investigation determined that a third party had copied payment card data stored on the platform.

Cleverbridge began notifying affected customers on November 20, sixteen days after detection. Its public page does not specify which card fields were taken, but the individual notification states that the card number, expiry date and card security code were involved, and that no names, contact details or billing addresses were copied.

The company told BleepingComputer the incident was not a ransomware attack and that no systems were encrypted. It says it has informed data protection authorities, law enforcement, card networks and payment partners, and is using TransUnion’s Cyberscout to send notifications and offer complimentary credit monitoring and fraud assistance. Cleverbridge did not answer BleepingComputer’s questions about the number of affected customers, the access method, whether stored card data was encrypted, or why security codes were retrievable.

Who is affected

Cleverbridge acts as a merchant of record for many software brands, so buyers frequently see the Cleverbridge name on card statements rather than the vendor they purchased from. BleepingComputer notes the company lists Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels among its customers, but Cleverbridge has not said which merchants’ buyers were impacted, and listing as a customer does not indicate exposure.

Malwarebytes is the only merchant reported so far to have confirmed impact, stating on its support forum that “only a small subset” of its customers were affected, according to security.hackerme.ai. The total number of affected cardholders has not been disclosed.

Severity and exploitation

The combination of card number, expiry date and security code is sufficient for most card-not-present transactions, which makes this data directly usable for online fraud. Industry rules under PCI DSS prohibit storing card verification codes after authorization, which is why the presence of CVV/CVC data in the stolen set has drawn attention; Cleverbridge has not explained how those codes came to be accessible. There are no public reports so far of the stolen data appearing for sale, and no threat actor has claimed the attack.

What defenders should do now

  1. Software vendors that sell through Cleverbridge should contact the company to determine whether their buyers were affected and prepare customer communications and support guidance.
  2. Organizations that purchase software licenses with corporate cards should check statements for Cleverbridge transactions since the start of the year and ask issuers to reissue any card that received a notification.
  3. Finance teams should review corporate card activity for small test charges and unfamiliar card-not-present purchases, and tighten per-card limits and merchant controls where available.
  4. Security teams should expect phishing that impersonates Cleverbridge or affected software brands and references the breach; warn staff not to provide card details in response.
  5. Merchants using any third-party checkout provider should confirm in writing what card data the provider retains, whether security codes are stored, and what the provider’s breach notification timelines are.

SCVM analysis

The Cleverbridge breach illustrates the concentration risk in outsourced checkout: one compromise at a merchant-of-record platform can expose buyers across many unrelated software brands, while those brands may learn the details only after their customers do. The most consequential open question is why security codes were available to be copied at all, since rules forbid retaining them after authorization. Until Cleverbridge discloses the access vector, the storage practices involved and the scale of the incident, enterprises should assume any card used for software purchases through the platform could be affected and act on that basis rather than waiting for a notification.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.