CoinSleuth

Gnosis Pay breach exposed card and wallet details; customer funds reportedly unaffected

If you use a Gnosis Pay card, the immediate concern is misuse of exposed card details or a phishing message that appears credible because it includes your personal information. In a report published on November 7, 2026, Cointelegraph said Gnosis Pay had disclosed unauthorized access to its legacy consumer card system.

Gnosis Pay said it detected the access on November 3 and began containing the breach within two hours. According to breach notifications reviewed by Cointelegraph, exposed information included full card numbers, expiration dates, CVV codes, names, home addresses and wallet addresses linked to affected accounts. The data also included email addresses, phone numbers and nationalities; some records contained IBAN and BIC banking details.

The company said customer funds and its separate enterprise platform were unaffected. One notification reviewed by Cointelegraph said that customer’s card was canceled on November 3 and that no suspicious transactions or movement of funds had been detected for that customer. That finding does not establish the outcome for every affected account. Gnosis Pay did not disclose how many customers were affected and had not immediately responded to Cointelegraph’s request for comment.

Gnosis Pay breach exposed card and wallet details; customer funds reportedly unaffected

Gnosis Pay said it replaced compromised security credentials, addressed the vulnerability and made 3D Secure verification mandatory for online payments until the legacy system’s planned retirement on December 20. It also warned customers about phishing using personal or transaction details and said it was arranging monitoring for potential misuse of the stolen data.

For scale—not as an estimate of affected customers—Cointelegraph cited OpenRate data showing around 2,400 daily active cardholders and $263,200 in transactions over the preceding 24 hours.

Source: cointelegraph.com (originally published 2026-11-07 04:51 UTC+8)

Further reading