Your Crypto Was Safe. Your Identity Wasn't.
Gnosis Pay lost no funds in its November breach — and that is exactly why the story matters.

The first line of Gnosis Pay's announcement was the good news.
Funds were not affected.
It was the second line that mattered. On November 3, someone got into the system behind Gnosis Pay's own branded cards and took customer information. The company contained it within two hours, rotated the affected credentials, fixed the vulnerability — and three days later, on November 6, it told the world.
Read that again slowly. The money was safe. The breach still happened. Both things are true at the same time, and the gap between them is the whole story.
Gnosis Pay sells a simple promise: a Visa card that spends crypto straight from your own wallet. Self-custody, they call it. Your coins stay in your hands, not on an exchange, not in a company vault. For a lot of crypto users, that promise is the entire reason the product exists. And on that promise, nothing went wrong. No wallets drained, no funds moved. The company says so, and nothing so far contradicts it.
But a card is never just a way to spend money. It is a file. A name, a home address, a card number, and — in this case — the wallet addresses linked to that card. One affected customer, the founder of the crypto portfolio tool Rotki, said the information taken from his account included exactly that: his name, his residential address, his card number, and the wallet addresses connected to his account.
Gnosis Pay itself has not published a customer count or a full list of what was taken. Every affected customer got an individual email on November 6 with the specifics of their own account. That is honest, and it is also the part worth sitting with: the company knows what was taken, and the rest of us don't. The breach is confirmed. The scale is not.
Here is the detail that stayed with me. The system that was breached was already dying. Gnosis Pay announced on September 21 that its consumer card business would shut down on December 20, 2026 — cards stop working at 23:59 UTC that day. The retirement was planned months before the breach. The system had 44 days left to live, and it was still holding live customer data when someone walked in.
Legacy systems are the softest targets in security, and everyone in the field knows it. They get the least attention, the fewest updates, the smallest budget — because the plan is always to replace them soon. Soon is a long time for an attacker. Gnosis Pay has now made 3D Secure mandatory for all online card payments until the shutdown, and stepped up monitoring of card activity and wallets. Those are the right moves. They are also moves that arrived after the fact, on a system that was already scheduled for the bin.
And there is a second incident in the background that the company has not connected to this one. In June, a separate exploit involving Gnosis Pay card accounts took about $1.5 million in digital assets. The company has not said the two incidents share a cause, and neither should I. But two incidents in five months on the same product line is a pattern a customer is allowed to notice, even if the causes turn out to be unrelated.
So what does this actually change for a cardholder? Less than the headlines suggest, and more than the good news implies.
Less, because the crypto itself was never the target here. Self-custody did its job. The coins stayed where they were. If you held a Gnosis Pay card because you didn't want an exchange holding your money, that reasoning still holds.
More, because the next attack almost certainly won't try to steal your crypto. It will try to steal your trust. Whoever holds a list of names, home addresses, card numbers and wallet addresses holds the raw material for phishing that sounds like it came from inside the company. An email that knows your card number and your wallet address doesn't look like spam. It looks like customer service. Gnosis Pay says neither it nor its partner apps will ever ask for your seed phrase, your private keys, your PIN, or your full card number. Remember that sentence. It is the one line that separates a real message from a fake one for the next few months.
If you got the email on November 6, read it properly — it tells you exactly what was taken from your account, and that list is more useful than any news article, including this one. If you didn't get one, you probably weren't affected, but the phishing wave that follows a breach like this doesn't check the list first. It mails everyone.
I'm still early in this field, and I keep a notebook of the cases that change how I think. This one goes in it under a short line: self-custody protects your coins. It was never designed to protect your identity. The card that couldn't be stolen from still had something worth taking — and it was the part nobody was watching.
Comments
Join the discussionThe "funds were not affected" line deserves exactly the skepticism you give it. Crypto can be made whole; identity data can't be rotated. A leaked KYC record - name, address, document image - is a permanent asset for whoever holds it, and its most immediate use is precision phishing: someone who knows you hold a specific card, knows your name, and can cite a real incident has everything needed to craft the follow-up "verify your account" email that actually lands. One thing worth adding to the response checklist for fintech breaches: a pre-planned user-communication channel that does not rely on email, because email is precisely the channel attackers will imitate in the days after the announcement. The first line of these statements tells you about the ledger. The second line tells you about the next six months of phishing.



