Foundation Links Passport Phishing Emails to Compromised Cloudflare API Keys

7Importance
closedStatus
8News media
Published
Updated

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

✓
Recipients said the emails contained personal and purchase details, and some were framed as urgent Passport recall notices.
✓
Foundation said the messages were meant to pressure recipients into revealing their seed phrases.
✓
Foundation said the phishing emails were sent from its own domains and were tied to at least one leaked Cloudflare API key.
✓
Foundation revoked all API keys late on October 25 after the phishing emails appeared.
✓
The company said it had recorded more than 23,000 malicious email attempts, with 19,057 sent through Mailgun and 1,503 through Google Workspace.
✓
Foundation said customer records were in systems the attackers could reach, but it had not found evidence that Passport devices or their private keys were affected.

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

Total crypto marketall crypto assets combined no single asset in the event: read against the whole market

The total crypto market rose 0.5% in the 4 hours after the first headline, after falling 0.2% in the 2 hours before.

$2.6T market cap at the headline
-0.2% 2 h before
+0.5% 4 h after
+2.6% 12 h after
First headline

47 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.

first
Oct 26 04:06
+3 h 14 m
Oct 26 07:19
crypto.news context
Its angle: enabled, remain, owners
+3 h 52 m
Oct 26 07:58
BeInCrypto context
Its angle: explanation, replacement, apparently; with quotes
+4 h 39 m
Oct 26 08:45
Unchained context
Its angle: vulnerability, newsletter, announced; with quotes
+5 h 25 m
Oct 26 09:30
CR Cryptopolitan echo
No new facts: transactions, transaction, contained; with quotes
+19 h 54 m
Oct 27 00:00
Crypto Economy context
Its angle: investigating, manufacturer, particularly; with quotes
+1 d
Oct 27 05:00
AMBCrypto echo
No new facts: cryptoverse, questions, another
+1 d 15 h
Oct 27 19:46
CP CryptoPotato echo
No new facts: interestingly, announcement, cautioned; with quotes

Other recent incidents

WhenWhat happenedFigure
2 days ago B18 TimeBank · Unknown incident $404.5k
3 days ago MORE Markets · Unknown incident $308k
3 days ago Lighter incident $10.4M
3 days ago Optimizely (OPTIMJACK) · Supply Chain Attack incident $2.3k
4 days ago Luxor Commander · Unknown incident no figure in dollars

4332 incidents stored