Cologne-based ecommerce firm Cleverbridge has begun notifying customers after a Cleverbridge breach in which, it says, a third party copied payment card data stored on its platform. In an undated incident update, the company wrote: “On 4 November 2026, Cleverbridge detected unauthorised activity in our platform.” It added that it “began notifying affected individuals on 20 November where appropriate.”
What Cleverbridge says happened
Cleverbridge describes itself as a global ecommerce provider that helps businesses manage online purchases, payments and subscriptions. If a customer bought a product or service from a business that uses the firm, Cleverbridge may have processed or managed that transaction.
The company says it took immediate steps to contain the incident and temporarily took affected systems offline. “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.” Asked whether the incident was a ransomware attack, it answered: “No. None of our systems were encrypted.”
The investigation, it says, remains ongoing. On the data involved, the FAQ is narrow: the information “may include payment card details used to make a purchase through Cleverbridge,” and affected people are told to refer to the notification they were sent for further details. Those notifications are being handled by TransUnion/Cyberscout, a third-party vendor Cleverbridge says it engaged to support customer notices. The company has offered credit or identity monitoring “where available,” and cardholders are directed to the letter they received for how to take up that offer.
Cleverbridge does not say how many people were affected, how the intruder got in, or how long the unauthorised access lasted before it was detected on 4 November. Those gaps matter. A same-day return to service does not, by itself, undo a copy of data that has already left the platform.
What the Cleverbridge breach notices say
Notices issued after the Cleverbridge breach are not uniform, and that is why the field-level detail should be read with care.
BleepingComputer, in a 22 November report by Lawrence Abrams, describes a notice listing “your card number, expiry date, card security code (CVV/CVC)” and stating that “no other personal data (for example your name, contact or billing details) were copied.”
CyberSIXT, however, has pointed out that the notices differ. One version, it says, states that the CVV was not copied but that contact details were; another says the CVV was copied but contact details were not. On the public record, then, it is not accurate to treat every affected customer as having lost the same fields, or to assume that every victim’s card security code was taken.
That inconsistency is awkward for readers trying to judge the risk. A copied CVV, if it was included in a particular notice, would make a dumped card number more immediately usable. Contact details, if they were included, would make phishing and social-engineering attempts easier to aim. Until Cleverbridge publishes a single, field-level account, the safest reading is the one the company already offers: look at the specific notice you were sent.
Malwarebytes confirms a limited impact among its customers
Cleverbridge has not published a list of the merchants whose transactions sit on the affected platform, and there is no reliable public basis for compiling one here. One vendor has spoken for itself. On the Malwarebytes support forum, a staff member posting as Root Admin confirmed that Cleverbridge processes payments for the security firm as a merchant-of-record processor, and wrote: “Only a small subset of Malwarebytes customers were impacted.” The same post directed people to Cleverbridge’s FAQ and said Malwarebytes had also contacted those of its customers who were affected.
That confirmation is useful, and it is also limited. It tells readers that at least one well-known software vendor’s checkout ran through the platform, and that the impact there was described as a small subset rather than the whole customer base. It does not fill in the missing totals for the wider Cleverbridge breach, and it is not a map of every business that uses the platform.
What affected customers should do
Cleverbridge’s own advice is straightforward. Check card statements carefully and tell the card issuer promptly about any transaction that is not recognised. Customers may also wish to tell the issuer about the incident, because the bank may choose to replace the card. The company warns people to be wary of unexpected emails, calls or messages about the incident, and says it will never ask for card details, passwords or security codes by email, phone or text message.
That last point is worth taking seriously after any payment-platform incident. Breach-themed phishing often follows public notifications: messages that mimic TransUnion, Cyberscout or a merchant, or that ask the recipient to “verify” a card in order to obtain a new one. The official route is the notice already received, the issuer’s own channels, and Cleverbridge’s published FAQ, rather than a link in an unexpected message.
The Cleverbridge breach is, on the company’s account, a copy of stored payment data rather than a ransomware lock-up, and systems were restored the same day the activity was detected. What remains unclear is the scale, the entry method and the dwell time. Until those points are answered, anyone who has received a notice should treat the card as compromised in the way that notice describes, watch statements, and treat unsolicited follow-up contact with suspicion.
Sources
- Cleverbridge, Incident Update & FAQs (undated; notifications from 20 November 2026)
- Cleverbridge, Legal Info (Cleverbridge GmbH, Cologne)
- Malwarebytes Forums, Cleverbridge Data Breach
- Lawrence Abrams, BleepingComputer, 22 November 2026
- CyberSIXT, Cleverbridge data breach
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- Accesso Ticketing Breach Hits LEGOLAND Korea and SEA LIFE Busan
- Prestige International Breach May Have Leaked 5.5m Roadside Records
- Keplr Says Some Social-Login Wallet Keys Were Breached
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X