Security News Cleverbridge Data Breach

Viking

Level 26
Verified
Honorary Member
Top Poster
Well-known
Forum Veteran

Incident Update & FAQs​

On 4 November 2026, Cleverbridge detected unauthorised activity in our platform and took immediate steps to contain the incident. Whilst our investigation remains ongoing, regretfully, we have been able to determine that a third party copied payment card data stored on our platform.

We worked diligently to identify individuals whose personal information may have been involved and began notifying affected individuals on 20 November where appropriate.

What happened?​


On 4 November 2026, Cleverbridge detected unauthorised activity in our platform. We took immediate steps to contain the incident, and affected systems were temporarily taken offline to address the issue. 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.

Who/what is Cleverbridge?​


Cleverbridge is a global ecommerce provider that helps businesses manage online purchases, payments, and subscriptions. If you have purchased a product or service from one of the businesses supported by Cleverbridge, Cleverbridge may have processed or managed that transaction.

What data was affected?​


Based on our investigation to date, the information involved may include payment card details used to make a purchase through Cleverbridge. Affected individuals should refer to the notification we sent them for further details.

Was this a ransomware attack?​


No. None of our systems were encrypted. 

Why does Cleverbridge have my data?​


Cleverbridge has your information because it was used in connection with a purchase or transaction you made with one of the businesses we support.

What should I do to protect myself if I was affected?​


We recommend that you check your card statements carefully and tell your card issuer right away about any transaction that you do not recognise. You may also wish to contact your card issuer to tell them about this incident and follow any advice they give, as they may decide to replace your card. 

As always, we recommend that our users follow general best online security practices, remain vigilant, and be aware of phishing attempts. Out of an abundance of caution, please be cautious of unexpected emails, calls, or messages about this incident. Cleverbridge will never ask you for your card details, passwords, or security codes by email, phone, or text message.
 
Incident Update & FAQs On 4 November 2026, Cleverbridge detected unauthorised activity in our platform and took immediate steps to contain the incident. Whilst our investigation remains ongoing, regretfully, we have been able to determine that a third party copied payment card data stored on our pla […]


Hi Viking. This is a confirmed data-exfiltration incident, not merely an attempted intrusion: Cleverbridge says a third party copied stored payment-card data. The notice is still frustratingly vague about the exact fields involved—card number, expiry date, cardholder name, or other transaction details—so affected customers should assume the card may be usable for fraud until their issuer says otherwise.

A couple of distinctions matter:

  • “Not ransomware” only means systems were not encrypted. It does not lessen the confirmed theft of data.
  • Restoring systems on 4 November does not establish that the intrusion began that day or lasted only one day. Cleverbridge has not provided that timeline.
  • The notice does not say passwords were exposed. Changing unrelated account passwords will not protect a copied card, although unique passwords and MFA remain sensible.

For anyone receiving an affected-customer notification, I would:

  1. Verify it independently through Cleverbridge’s official website or support channel—do not use links or telephone numbers in an unexpected message.
  2. Contact the card issuer using its app or the number printed on the card. Given the confirmed copying and lack of detail, requesting a replacement card is the prudent option, particularly for a debit card.
  3. Lock the card temporarily if that facility is available, enable instant transaction alerts, and inspect recent and future statements.
  4. Report even small unfamiliar charges promptly; criminals sometimes use low-value transactions to test whether a card works.
  5. Treat follow-up messages about refunds, “verification,” or breach compensation as suspicious. Neither Cleverbridge nor a bank needs a password, PIN, complete security code, or one-time authentication code sent back by email, text, or telephone.

A credit freeze is not a substitute for replacing the card: it can help against new-account identity fraud, but generally does not stop fraudulent use of an existing card number. More information from Cleverbridge—especially the precise data fields, affected transaction dates and number of people notified—is still needed.
 
@Bot can we assume all those who were affected will be notified by Cleverbridge, do they have an exact list of breached accounts? And with something like this, do the hackers attempt to access the accounts as soon as possible, before this information reaches more people and they make the appropriate safeguard changes, or, could they try to access accounts a month or two later, after some of the dust settles?

F-Secure uses them.
 
@Bot can we assume all those who were affected will be notified by Cleverbridge, do they have an exact list of breached accounts? And with something like this, do the hackers attempt to access the accounts as soon as possible, before this information reaches more people and they make the appropriate safeguard changes, or, could they try to access accounts a month or two later, after some of the dust settles? F-Secure uses them.


No, I would not assume every affected person will definitely receive a notification. Cleverbridge says it identified people whose data may have been involved and began notifying them “where appropriate,” while also saying the investigation remains ongoing. That suggests it has a working affected population, but it does not confirm a complete, exact list.

Notifications can also fail because contact details are outdated, and legal notification criteria vary. Conversely, merely having bought F-Secure, Malwarebytes, or another product that uses Cleverbridge does not mean that transaction was in the compromised data set. No email is reassuring, but it is not proof of being unaffected.

Also, the disclosed issue concerns payment-card data, not necessarily F-Secure or Cleverbridge login credentials. The notice does not say account passwords were copied. Criminals might:

  • test or use card details quickly, before cards are replaced;
  • sell them to others, creating a delay;
  • wait weeks or months, including to make fraudulent charges harder to associate with this breach.

Card data tends to lose value as issuers detect the breach and replace cards, so prompt use is common—but delayed fraud is entirely plausible. Anyone notified should contact the card issuer using the number on the card or its official app and ask whether replacement is recommended. Transaction alerts and statement checks should continue for the remaining life of the card, not merely while this is in the news.

The key unanswered questions for Cleverbridge are the compromised card fields, affected transaction dates, and whether its notification population is now complete. Until it publishes those details, an “exact list of breached accounts” is more than the notice supports.
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,693 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top