Rotki Founder Says Gnosis Pay Exposed His Address, Card and Wallet Details
- Published
- Updated
Gnosis Pay disclosed a breach in its consumer-card system after unauthorized access on Nov. 3, while saying customer funds and its enterprise platform were not affected. New coverage adds that the incident involved the legacy system behind its branded cards, with some reports also describing exposed card details, home addresses, and linked wallet data.
Key claims & sources
What it means
Gnosis Pay built its card around self-custody: users link a Gnosis Safe wallet to a Visa-branded debit card, spending crypto without handing funds to a custodian. That design required a separate 'legacy' back-office layer to run KYC checks, store addresses and card numbers, and match identities to wallets for compliance. That older B2C system, distinct from the newer enterprise platform used by white-label partners, is the one Gnosis Pay says intruders reached on Nov. 3.
Cardholders now face a narrower but sharper risk: not stolen crypto, but exposed names, home addresses, card numbers and the wallet addresses tied to them. That combination lets attackers run targeted phishing or SIM-swap attempts, and because wallet addresses are public ledgers, it can deanonymize on-chain activity that users assumed was pseudonymous. Affected users should expect replacement cards, monitor for phishing emails, and treat any linked wallet as potentially identifiable going forward. (per cointelegraph.com)
A card that holds no custody of funds still depends on a centralized back office that holds everything about the person behind the wallet. Gnosis Pay's repeated insistence that 'funds are safe' sidesteps the deeper point: pairing a non-custodial wallet with a KYC'd card reintroduces the single point of failure crypto payments were meant to avoid, just moved from the asset layer to the identity layer. (per u.today)
Gnosis Pay says extra security checks will stay in place on the legacy system until its planned shutdown on Dec. 20, when the infrastructure behind the breach is retired rather than patched. Watch whether the company discloses a customer count before that date, and whether the enterprise platform it says was untouched absorbs the B2C business without repeating the same identity-data exposure.
Market reaction i
Gnosis fell 1.1% in the 4 hours after the first headline, after rising 0.2% in the 2 hours before.
48 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Protos
context
Decrypt
echo
U.Today
echo
Crypto Economy
context
Cointelegraph
echo
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 3 days ago | Degen Coin Flip · Smart contract vulnerability incident | $10k |
| 4 days ago | FLOKI Trading Bot incident | no figure in dollars |
| 4 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 4 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 6 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
4285 incidents stored