Foundation Links Passport Phishing Emails to Compromised Cloudflare API Keys
- Published
- Updated
- Since then
- 7 new reports
Foundation said phishing emails sent to Passport customers were traced to compromised Cloudflare API keys and appeared to come from its own domains. New coverage says the incident also raised data-privacy questions after customer records were exposed in systems the attackers could reach, even as the company said Passport devices and the Bitcoin held in them were not affected.
Key claims & sources
What it means
Foundation builds Passport, a Bitcoin-only hardware wallet that competes with Ledger and Trezor on the promise that private keys never touch a server. The Cloudflare breach echoes Ledger's 2020 data leak, when a marketing database exposed customer names and addresses and fed years of phishing and physical threats. Hardware wallet makers sell security as their core product, so a breach of their own backend, not the device, cuts at the same trust.
Passport owners who received the fake recall notice now have to treat any email from Foundation's domains with suspicion until the company confirms its systems are clean, and must never enter a seed phrase in response to an unsolicited prompt. Foundation has to rotate the compromised Cloudflare API keys, audit who else touched its backend, and explain how personal and purchase data reached attackers in the first place. Customers who ignored the recall email keep their funds; those who complied face the real risk.
A Bitcoin-only wallet marketed on self-custody still depends on cloud infrastructure like Cloudflare to run customer-facing systems, and that dependency is where attackers found an opening, not the hardware itself. Exposed home addresses tied to purchase records raise the same physical-safety concern that followed Ledger's breach, where leaked data enabled real-world targeting of known crypto holders. The incident is a reminder that 'cold storage' security claims rarely extend to the company's own email and billing stack.
Foundation has promised a fuller incident report following its Sunday disclosure on X, and that document should spell out how the Cloudflare keys were obtained and whether customer data beyond emails and addresses was taken. Whether Cloudflare identifies a shared vulnerability across other API customers, or the breach stays isolated to Foundation's account, will determine if this becomes a single-vendor failure or a wider warning for companies relying on the same infrastructure.
Market reaction i
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.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | Loopscale Lending · Unknown incident | no figure in dollars |
| 1 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 1 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 3 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
| 4 days ago | Solana MEV Bot King · Hot wallet key compromise incident | $856k |
4280 incidents stored