TechPastWeek logo
Security8 min read

Cleverbridge Says Attackers Copied Card Numbers and CVVs From Its Checkout Platform

Cleverbridge says a third party copied card data from its checkout platform. Notifications quoted by BleepingComputer list card numbers, expiry dates and CVVs.

A bank card with a visible chip resting on the keyboard of an open laptop.
On this page

Key takeaways

  • Cleverbridge detected unauthorised activity on 4 November 2026 and later found that a third party had copied payment card data stored on its platform. It began notifying affected buyers on 20 November.
  • A notification quoted by BleepingComputer says the copied data includes the card number, expiry date and CVV/CVC security code, and that names, contact details and billing details were not taken.
  • Cleverbridge processes payments for software and SaaS vendors including Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels. It has not said which storefronts or how many buyers are affected.
  • The company says the incident was not ransomware, that no systems were encrypted, and that it has notified data protection authorities, law enforcement, card networks and payment partners.
  • CVVs are sensitive authentication data that PCI DSS prohibits retaining after a transaction is authorised, which makes their theft a direct card-fraud risk and gives issuers a reason to replace cards.

Cleverbridge, which runs checkout and subscription billing for software companies, has told customers that a third party copied payment card data from its platform, including card numbers and the security codes used to verify online purchases.

Related reading: OpenRouter Cut Three Providers After Prompts Leaked Across Its Supply Chain · The FBI Is Investigating an Apparent Breach of Its Crime Database.

The company detected unauthorised activity on 4 November 2026 and took affected systems offline that day. It began notifying buyers on 20 November, and its public incident page now says the investigation found that card data stored on the platform had been copied. The page does not list which card fields were involved or how many people were affected.

A notification quoted by BleepingComputer is more specific. It says the data includes the card number, expiry date and CVV/CVC security code, and that names, contact details and billing details were not copied. Cleverbridge has not published that list itself, and it did not answer BleepingComputer's questions about the number of affected customers, the entry point, whether the card data was encrypted, or why CVVs were accessible.

What the company has confirmed

Cleverbridge says it found unauthorised activity on 4 November, contained it, and brought all systems back online the same day. The investigation continued after service was restored, and it was that work which established the theft.

"All systems were brought back online on 4 November 2026; however, our investigation subsequently determined that a third party copied payment card data stored on our platform," the incident page says.

Cleverbridge describes itself as a global ecommerce provider that manages purchases, payments and subscriptions for other businesses. It says it has notified data protection authorities, law enforcement, card networks and payment partners. It is using TransUnion's Cyberscout to send notifications and to offer credit or identity monitoring where available.

The company says the incident was not a ransomware attack and that none of its systems were encrypted, which rules out one kind of damage, not the theft itself.

Its advice is standard: check statements, report unfamiliar transactions, and be suspicious of messages that use the breach as a hook. The page says Cleverbridge will never ask for card details, passwords or security codes by email, phone or text.

Why the CVV changes the risk

A stolen card number is a problem. A stolen number with its expiry date and CVV is a more complete instrument for fraud.

The CVV is the three- or four-digit code printed on the card and used as an extra check in card-not-present transactions. Under PCI DSS it is sensitive authentication data, and the standard says card verification codes must not be stored after a transaction is authorised, including for card-on-file or recurring payments. Requirement 3.3.1 is explicit: sensitive authentication data is not retained after authorisation, even if encrypted.

A CVV is most useful at the moment of purchase. A merchant that keeps one creates a store of data that can be replayed if its systems are breached. Cleverbridge has not said why a CVV was present, where it sat, or whether the data was encrypted at rest. BleepingComputer asked; the company did not answer.

A CVV does not guarantee that every fraudulent attempt will succeed. Issuers still apply risk scoring, and many merchants add a 3-D Secure or one-time-code step. But number, expiry and CVV are exactly what many checkout forms ask for, and the code removes one check that makes a bare card number harder to use.

One checkout behind many software brands

Cleverbridge is a merchant of record. In that model, the company is the legal seller of the software, handles tax and currency, and processes the payment. Its client stories page lists Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels, among others.

The model explains why one breach reaches beyond one company's customers. Cleverbridge's own description of the merchant-of-record role says client systems receive customer and transaction details "except full credit card numbers", which shields the software vendor from much of the PCI DSS burden. The full number stays with the merchant of record.

Software companies outsource payment security to a specialist and stop holding the most sensitive data themselves. Their customers' exposure then depends on how that specialist stores and protects the data. A single incident can reach buyers across many storefronts, including people who know the name only from a billing line.

Cleverbridge has not said which clients' customers were affected. BleepingComputer asked and got no answer. The listed companies are customers of the platform, not confirmed victims, and none has been named as part of the notification pool.

Sixteen days between detection and notification

The gap between 4 November and 20 November is the part affected buyers are most likely to ask about. Cleverbridge says it acted "without undue delay" once it had identified the people whose information may have been involved. The company has said it notified data protection authorities, but its page does not say when.

European rules set two clocks. A controller must tell its supervisory authority about a personal data breach within 72 hours of becoming aware of it, unless the breach is unlikely to put people at risk. Individuals must be told without undue delay when the breach is likely to put them at high risk. Both obligations are in Article 33 and Article 34 of the GDPR.

The 16-day gap is not proof of a violation. Identifying which cardholders were affected can take time, and the 72-hour clock applies to the authority notification, not the customer letter. But the public page gives no dates for either step, so an outside reader cannot check the timeline.

A separate card-data incident a year earlier

This is not Cleverbridge's first breach notification involving payment information.

In October 2025, Turkey's Personal Data Protection Authority published a Cleverbridge GmbH notification covering 1,235 people. The authority's announcement says the breach occurred on 10 September 2025 and was detected on 15 September, after unusual use of an API from an unknown IP address. A summary published by CyberArts lists names, company, email address, payment method, the card's last four digits, expiry date, pricing details and recurring billing details among the affected data.

That incident involved partial card details, not full numbers and CVVs. The current notification, as quoted by BleepingComputer, involves the full card number and the security code. No source has connected them.

It shows that the company has handled a card-data investigation before, that its API was abused in the past, and that a regulator has published a fuller account than the company did. Whether the same will happen in Germany, where Cleverbridge GmbH is based, is unknown.

What Cleverbridge has not said

The company has not disclosed the number of affected buyers, the storefronts involved, the date range of the purchases whose card data was copied, the method of intrusion, how long the intruders had access, whether the card data was encrypted, whether card networks have imposed any penalties, or why CVVs were present at all. It has not said whether the notification pool is complete.

The difference between its public page and the private notification matters. The page says the information "may include payment card details". The notification says the card number, expiry date and CVV were taken. Buyers who did not receive a letter have only the vaguer public version to work from.

What buyers and businesses should do

Anyone who receives a Cleverbridge notice should treat the card they used as exposed. Call the issuer using the number on the card, not one from an unexpected email, and ask whether it should be replaced. Turn on transaction alerts and check for small test charges as well as large ones. Cleverbridge warns that phishing messages may reference the incident.

Buyers who got no notice are in a harder position. The absence of a letter is not evidence that a card was safe, because the company has not said how it chose recipients. The practical step is the same: watch the statement and ask the issuer.

Businesses that use Cleverbridge should ask for the incident report and the scope of the notification pool, and should confirm whether their own customers' card data was tokenised or stored in full. A vendor's PCI DSS attestation covers the controls it had at the time of assessment; it is not a statement that no data was taken.

Caveats

The field-level details come from a notification BleepingComputer obtained and quoted. The company's public page confirms that payment card data was copied but does not list the fields. No independent forensic report has been published, no attacker has been named, and the number of affected buyers is unknown.

Cleverbridge says the incident was not ransomware; that is a statement about encryption, not about the completeness of the theft. The 2025 KVKK notification is a separate incident, and no link between the two has been established. The GDPR timeline discussion describes the general rule, not a finding that Cleverbridge missed a deadline. PCI DSS compliance is assessed by the card industry, and a breach does not by itself prove non-compliance.

"All systems were brought back online on 4 November 2026; however, our investigation subsequently determined that a third party copied payment card data stored on our platform." — Cleverbridge, incident update

Cleverbridge says its investigation remains ongoing. The page does not say when it will be finished.

Cover image: a bank card resting on a laptop keyboard. Photo by Shixart1985, CC BY 2.0, via Wikimedia Commons.

Tags

data-breachpayment-cardscleverbridgemerchant-of-recordpci-dss

Frequently asked questions

What happened in the Cleverbridge data breach?
Cleverbridge detected unauthorised activity in its platform on 4 November 2026. Its investigation found that a third party copied payment card data stored on the platform, and it began notifying affected buyers on 20 November.
Was my card affected if I bought software through Cleverbridge?
Cleverbridge has not published which storefronts or how many buyers were affected. If you received a notification from Cleverbridge or its agent TransUnion/Cyberscout, treat the card you used as exposed. If you did not, that is not proof the card was safe.
Did Cleverbridge store CVV security codes?
The notification quoted by BleepingComputer says the card security code was copied. Cleverbridge has not explained why a CVV was present on its platform, and PCI DSS generally forbids keeping one after a transaction is authorised.
What should I do if I get a Cleverbridge breach notice?
Check the card statement for unfamiliar charges, call the issuer using the number printed on the card, and ask whether the card should be replaced. Cleverbridge says it will never ask for card details, passwords or security codes by email, phone or text.
Share

Found this useful? Share it with your team.

TPW Editorial

TPW Editorial

Editorial Team

TechPastWeek's editorial team reports and edits every story we publish. We research each piece against primary and credible secondary sources, and a human editor reviews and signs off before it goes live.

Keep reading