Cleverbridge, which handles checkout, payments and subscription billing for software and SaaS vendors, has confirmed that an unauthorised third party copied payment card data stored on its platform. On a public incident page, the company says it detected the intrusion on 4 November 2026 and began notifying affected cardholders on 20 November. A customer notification seen by BleepingComputer says the stolen data includes full card numbers, expiry dates and CVV/CVC security codes. Cleverbridge has not said how many people are affected, which merchants' customers were hit, or how the attackers got in. Malwarebytes has confirmed that some of its customers are among those notified.
What Happened
Cleverbridge's public disclosure gives a short timeline. The company spotted unauthorised activity on 4 November 2026 and briefly took systems offline to contain it. "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 disclosure reads, as quoted by BleepingComputer.
Notifications to affected cardholders started on 20 November, 16 days after detection. Cleverbridge has since published an FAQ at grow.cleverbridge.com/incident-update. A Malwarebytes forum administrator pointed customers to the FAQ after users asked whether the notification emails were genuine.
Ukrainian outlet Mezha, citing BleepingComputer's reporting, says Cleverbridge stated the incident was not ransomware and that its systems were not encrypted. According to the same report, the company has notified data protection authorities, law enforcement, the card networks and its payment partners. It is using TransUnion's Cyberscout to send notifications and to offer free credit monitoring and fraud help. One Malwarebytes customer posting on the company's forum said the notification offered two years of credit monitoring.
Who is affected. Cleverbridge processes payments as merchant of record for many technology brands. It lists Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels among its clients. Being on that list does not mean a company's customers were affected, and Cleverbridge has not named any affected merchants. Malwarebytes is the only vendor that has publicly confirmed impact so far. A forum administrator there said "only a small subset of Malwarebytes customers were impacted" and stressed that "this was a breach of Cleverbridge systems." Anyone who has paid a Cleverbridge-billed vendor may be in scope. Those charges often appear on card statements as "CBI" followed by the vendor name, for example CBIPARALLELS for Parallels Desktop purchases.
What Was Taken
Cleverbridge's public page confirms only that "payment card data" was copied, and it refers individuals to their own notifications for details. The notification shared with BleepingComputer is more specific:
- Full payment card number (the notice names the card by its last four digits)
- Expiry date
- Card security code (CVV/CVC)
The same notice says "no other personal data (for example your name, contact or billing details) were copied."
Volume: Cleverbridge has not disclosed it. BleepingComputer asked the company how many customers were affected and had not received an answer at the time of reporting. No regulator filing with a count has appeared, so the scale of the breach is currently unknown.
Sensitivity: This data is close to the most useful card data an attacker can get. Card number, expiry and CVV together are enough for most card-not-present fraud. Stolen cardholder names would normally add value, but many merchants do not check them strictly. Subscription billing also makes the risk last longer: renewal cards stay active for months or years, and the Malwarebytes forum user who raised the alarm noted that the card on file was one they had only recently replaced after an earlier fraud incident.
Why It Matters
CVV codes should not have been there to steal. PCI DSS forbids keeping card security codes after a transaction is authorised. Cleverbridge describes the data as "stored on our platform," but the notification says CVVs were taken. That leaves three possibilities: security codes were being kept against the standard, the attackers captured data as it moved through the platform rather than from storage, or Cleverbridge's wording is loose. The company has not explained which. Card brands and acquiring banks will press this question, and it is the most important open technical point in the incident.
One payment provider, many vendors' customers. Merchant-of-record platforms gather the card data of thousands of software vendors in one place. A single breach at the processor reaches buyers of products from many unrelated companies. Most of those buyers have never heard of Cleverbridge and only see a "CBI*" line on their statement. That makes it harder for victims to understand the notification, and easier for scammers to impersonate it. Malwarebytes users had to ask on a forum whether the email was real.
Part of a busy month for payment data. Separately, fashion retailer Revolve disclosed earlier in November that card numbers and expiry dates were stolen. A Texas attorney general record suggests about 1.5 million people may be affected, although Malwarebytes notes that Revolve has not confirmed that figure. In Brazil, Sansec tied a Magecart skimmer planted in e-commerce platform Convertr's self-hosted analytics script to a group it has tracked since 2024. That skimmer took card numbers, CVVs and taxpayer IDs from 24 to 27 October. Also this week, J.P. Morgan Chase, Visa and Mastercard each said third-party providers had suffered incidents exposing marketing or contact data, though not card numbers. Nothing publicly links any of these to Cleverbridge. Together, though, they show attackers repeatedly going after the vendors and platforms in the payment chain rather than the brands customers deal with directly.
The Attack Technique
This part is mostly unknown. Cleverbridge has not said how the attackers got in, how long they were inside before detection, or whether the card data was taken from a database, from logs, or while transactions were being processed. What the company has said, as relayed by Mezha:
- The incident was not ransomware, and nothing was encrypted.
- The goal appears to have been quietly copying data, not disruption. Systems were back online the same day the intrusion was detected.
- The intrusion was found on 4 November. The full scope, meaning that card data had been copied, became clear only through later investigation.
No threat actor has claimed the attack, and no leak site listing or underground sale of Cleverbridge data has been reported. Until Cleverbridge or a regulator publishes more, any attribution or account of how the attackers got in is guesswork. The Convertr case shows one way processors and checkout platforms have been hit recently: a single tampered script served to every payment page. It is a separate incident, though, and there is no evidence the same method was used here.
What Organizations Should Do
-
Check whether you rely on Cleverbridge. Software and SaaS vendors that use it as merchant of record should ask Cleverbridge directly whether their customers are affected and how many. Prepare customer messaging now rather than waiting for buyers to find "CBI*" on their statements. Corporate finance and procurement teams should check whether company cards were used for software bought through the platform.
-
Reissue affected cards rather than watching them. When the CVV has been taken, monitoring is a weak control. Card issuers and corporate card programme managers should proactively replace cards identified in notifications. Cleverbridge itself says banks may choose to do this. Credit monitoring, which is on offer, does little against card-not-present fraud.
-
Get ahead of the phishing that follows. Tell staff and customers that genuine notices come from Cleverbridge and its partner Cyberscout. Neither Cleverbridge nor the affected vendors will ask anyone to re-enter card details, CVVs or passwords. Malwarebytes has already given its customers this warning. Watch for lookalike domains and "update your payment method" lures that use the Cleverbridge or CBI name.
-
Check where security codes might be kept in your own environment. If you handle card data, confirm that CVVs never persist after authorisation. That includes application logs, debug traces, message queues, data warehouse copies and backups. These are the places where "we don't store it" often turns out to be untrue.
-
Lock down payment-page scripts and third-party access. Apply the PCI DSS v4 controls on payment pages: keep an inventory of every script, authorise each one, check their integrity and alert on changes. Also review the access your payment providers and other vendors have into your environment. Recent incidents involving Convertr and the vendors behind the Chase and Plaid/KARTE breaches show that weaknesses at a supplier become your exposure.
-
Ask your payment processors the hard questions now. Ask for current PCI compliance evidence and a description of how they handle security codes. Ask for their breach notification terms, including a commitment to tell merchants who is affected and how many. A 16-day gap between detection and notification with no victim count is a good example of what to write into contracts.
Sources: Cleverbridge warns hackers stole credit card numbers, CVVs in data... | Vendor data breach exposes Chase, Visa, Mastercard customer info | Cleverbridge Data Breach - Malwarebytes for Windows Support Forum -... | Cleverbridge says hackers stole customers’ payment card data Межа | Revolve card breach: 1.5 million people may be affected Malwarebytes | What Is CBI Parallels Charge On Credit Card? | 当社が利用する外部サービスへの不正アクセスに伴う個人情報漏えいについて(第三報) | Convertr's own analytics script skimmed checkout cards Yaamlabs