Skip to main content
All incident reports
Incident report

Cleverbridge says hackers copied card numbers and CVV codes from its checkout platform

Cleverbridge, which handles checkout and subscription billing for software companies, says a third party copied payment card data from its platform. Notification letters sent to customers say card numbers, expiry dates and CVV security codes were taken.

· First published

The short version

  • The breach. Cleverbridge detected unauthorised activity on its platform on 4 November 2026 and took systems offline to contain it. Its investigation later found that a third party had copied payment card data stored on the platform.
  • What was taken. A breach notification seen by BleepingComputer says the copied data includes card numbers, expiry dates and CVV/CVC security codes. Cleverbridge says names, contact details and billing details were not copied.
  • Who is affected. Cleverbridge began notifying affected customers on 20 November. It has not said how many people are affected or which of its software clients' customers are involved.
  • The company's response. Cleverbridge says the incident was not ransomware and no systems were encrypted. It says it has notified data protection authorities, law enforcement, card networks and payment partners, and is offering credit monitoring through TransUnion's Cyberscout.

Timeline

DateEvent
4 NovCleverbridge detects unauthorised activity and takes systems offline; all systems are back online the same day.
20 NovCleverbridge begins notifying affected customers that their payment card data was copied.
22 NovBleepingComputer reports the breach after obtaining a copy of the customer notification.

What happened

Cleverbridge runs e-commerce services for software and SaaS companies, processing payments and managing subscriptions on their behalf. On 4 November 2026 it detected unauthorised activity, took systems offline and brought them back the same day. Its investigation then established that a third party had copied payment card data held on the platform.

The public incident page confirms card data was stolen but does not list the fields. A notification sent to an affected customer and shared with BleepingComputer is more specific: the card number, expiry date and CVV/CVC security code were involved, and no name, contact or billing details were copied. The notification identifies the affected card by its last four digits.

Cleverbridge says the incident was not a ransomware attack and that no systems were encrypted. It has not said how the attackers reached its platform, how long they had access, or whether the card data was encrypted while stored.

Who is affected

Those affected are people who used Cleverbridge's checkout to buy from a software or SaaS vendor. Cleverbridge names Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels among the technology brands it serves, but has not disclosed which of their customers received notifications.

The exposure is limited to payment card details, according to the notification. The presence of CVV/CVC codes among the stolen data is notable because those codes are used to verify payment card transactions.

What Cleverbridge has done

Beyond notifying customers, Cleverbridge says it has contacted data protection authorities, law enforcement, the card networks and its payment partners. It is working with TransUnion's Cyberscout to send the notifications and to provide complimentary credit monitoring and fraud assistance.

Affected customers are advised to check their card statements for unauthorised transactions and to contact their card issuer, which may decide to replace the card. BleepingComputer asked Cleverbridge how many customers were affected, how the attackers got in, whether the data was encrypted and why CVV/CVC codes were accessible; the company had not responded when the article was published.

What is not known yet

  • Who carried out the intrusion, and whether they were a criminal group or an individual.
  • How the attackers gained access to the platform and how long they were inside it before detection on 4 November.
  • How many customers had card data copied, and which client brands' customers are among them.
  • Whether the stored card data, including the security codes, was encrypted at rest.
  • Whether any of the stolen card details have since been used for fraudulent transactions.

What to do

If you bought software through Cleverbridge

  1. Check the notification you received for the last four digits of the affected card so you know which card to watch.
  2. Review that card's statements for transactions you do not recognise and report any to your card issuer.
  3. Contact your card issuer about the incident and ask whether the card will be replaced.
  4. Use the credit monitoring and fraud assistance offered through TransUnion's Cyberscout in the notification.

If your company sells through Cleverbridge

  1. Ask Cleverbridge which of your customers were notified and on what dates.
  2. Brief your support and customer-facing teams so they can answer questions about the incident and point customers to Cleverbridge's notification.
  3. Direct customers to the contact details in their own notification rather than collecting card details yourself.

For everyone else

  1. Ask the payment and checkout providers you use whether they store card security codes, and for how long.
  2. Review how many third parties hold your customers' card data and whether each of them needs to.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

We email you about this topic only; unsubscribe any time. See our Privacy Policy.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.