<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Recovery Phrase - PhishFort</title><link>https://phishfort.com/resources/blog/tag/recovery-phrase/</link><description>PhishFort delivers agentic brand protection: detecting and eliminating phishing sites, fake apps, and impersonations across every digital channel.</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Mon, 02 Nov 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://phishfort.com/resources/blog/tag/recovery-phrase/index.xml" rel="self" type="application/rss+xml"/><item><title>Foundation Passport Phishing: Fake Recall Emails Explained</title><link>https://phishfort.com/foundation-passport-phishing-data-retention/</link><pubDate>Sun, 01 Nov 2026 13:00:00 +0000</pubDate><dc:creator>PhishFort Team</dc:creator><guid>https://phishfort.com/foundation-passport-phishing-data-retention/</guid><description><![CDATA[<p><em>By PhishFort Team · Last updated: November 1, 2026</em></p>
<p>On October 25, 2026, attackers sent more than 23,000 phishing emails to customers of Foundation, the maker of the Passport bitcoin hardware wallet, from the company&rsquo;s own domains. The fake recall notices used real names and home addresses to push recipients toward a site that asked for their recovery phrase. Foundation says Passport devices and funds were not compromised.</p>
<h2 id="summary">Summary</h2>
<ul>
<li>Foundation first blamed compromised Cloudflare API keys, then pointed to a vulnerable self-hosted app. A full report is pending.</li>
<li>The leaked customer details came from old store records that survived Foundation&rsquo;s 60-day deletion rule in hidden database copies.</li>
<li>The breach did not touch private keys. The risk is targeted phishing and physical threats to owners whose addresses leaked.</li>
</ul>
<h2 id="what-happened-in-the-foundation-passport-phishing-attack">What happened in the Foundation Passport phishing attack?</h2>
<p>The emails arrived on Sunday, October 25, with subject lines such as &ldquo;Your Passport funds are at risk&rdquo; and &ldquo;Urgent recall notice.&rdquo; They claimed a tampered display module was draining funds, offered a free replacement and linked to <code>foundation[.]support</code>, a fake site that copied Envoy, Foundation&rsquo;s companion wallet app. The site showed an empty wallet with a deposit button and asked visitors to create a wallet or enter their recovery phrase.</p>]]></description><content:encoded><![CDATA[<p><em>By PhishFort Team · Last updated: November 1, 2026</em></p>
<p>On October 25, 2026, attackers sent more than 23,000 phishing emails to customers of Foundation, the maker of the Passport bitcoin hardware wallet, from the company&rsquo;s own domains. The fake recall notices used real names and home addresses to push recipients toward a site that asked for their recovery phrase. Foundation says Passport devices and funds were not compromised.</p>
<h2 id="summary">Summary</h2>
<ul>
<li>Foundation first blamed compromised Cloudflare API keys, then pointed to a vulnerable self-hosted app. A full report is pending.</li>
<li>The leaked customer details came from old store records that survived Foundation&rsquo;s 60-day deletion rule in hidden database copies.</li>
<li>The breach did not touch private keys. The risk is targeted phishing and physical threats to owners whose addresses leaked.</li>
</ul>
<h2 id="what-happened-in-the-foundation-passport-phishing-attack">What happened in the Foundation Passport phishing attack?</h2>
<p>The emails arrived on Sunday, October 25, with subject lines such as &ldquo;Your Passport funds are at risk&rdquo; and &ldquo;Urgent recall notice.&rdquo; They claimed a tampered display module was draining funds, offered a free replacement and linked to <code>foundation[.]support</code>, a fake site that copied Envoy, Foundation&rsquo;s companion wallet app. The site showed an empty wallet with a deposit button and asked visitors to create a wallet or enter their recovery phrase.</p>
<p>The messages came from real Foundation addresses, such as hello@ and <a href="mailto:jobs@foundation.xyz">jobs@foundation.xyz</a>, which helped them pass spam filters. Many included full names, phone numbers, postal addresses and past orders.</p>
<h3 id="how-did-foundation-explain-the-breach">How did Foundation explain the breach?</h3>
<p>Foundation&rsquo;s first statement, late on October 25, blamed &ldquo;one or more compromised API keys on Cloudflare.&rdquo; It revoked the keys and had the malicious domain taken down. About two hours later, CEO Zach Herbert said attackers had broken into backend infrastructure through a vulnerability in a self-hosted app and likely reached the customer support inbox.</p>
<p>On October 26, Foundation counted more than 23,000 sending attempts, mostly through Mailgun. Some people got several copies, so the number of affected customers is unknown.</p>
<h2 id="why-does-a-data-leak-matter-if-the-hardware-wallet-is-safe">Why does a data leak matter if the hardware wallet is safe?</h2>
<p>A hardware wallet keeps private keys offline, but it cannot stop an owner from typing the recovery phrase into a fake site. An email from the maker&rsquo;s real domain, carrying the buyer&rsquo;s name and order, removes the usual warning signs. PhishFort has explained <a href="https://phishfort.com/can-a-hardware-wallet-get-phished/" target="_blank" rel="noopener">how a hardware wallet can still be phished</a>. The lure is not new: in August, attackers used the <a href="https://phishfort.com/coldcard-phishing-hardware-audit-scam/" target="_blank" rel="noopener">Coldcard entropy incident</a> the same way.</p>
<p>A leaked home address adds a physical risk. Bitcoin developer Jameson Lopp keeps a <a href="https://github.com/jlopp/physical-bitcoin-attacks" rel="nofollow">public list of physical attacks on crypto holders</a>, often called wrench attacks. Exposing wallet owners is a security problem, not only a privacy one.</p>
<h2 id="why-did-customer-data-that-foundation-said-it-deleted-still-leak">Why did customer data that Foundation said it deleted still leak?</h2>
<p>In March 2022, Foundation <a href="https://x.com/FoundationHQ/status/1506353093067395087" target="_blank" rel="noopener">said on X</a> that it deletes customer data 60 days after an order ships. Its investigation explains the gap: the old WooCommerce store did anonymize orders after 60 days, and the admin panel showed them as deleted, but earlier database migrations had copied the records into auxiliary tables outside that view. Those copies kept names, contact details, addresses, refunds and abandoned carts.</p>
<p>
















  
  
  
    
    
    

    
    

    
      
      
      
      
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
      
      

      <picture>
        <source srcset="/img/1793630117026-pasted-image_hu_507a3a2c344d8641.webp 480w, /img/1793630117026-pasted-image_hu_5afbad1720fe6f10.webp 768w, /img/1793630117026-pasted-image_hu_3051e2099d1ce93c.webp 1200w, /img/1793630117026-pasted-image_hu_110e18e04dd2316.webp 1600w, /img/1793630117026-pasted-image_hu_4a07e24a4ca13a69.webp 2000w, /img/1793630117026-pasted-image_hu_90dba081d255c522.webp 2048w"
                sizes="(max-width: 768px) 100vw, 700px" type="image/webp">
        <img src="/img/1793630117026-pasted-image.png"
          srcset="/img/1793630117026-pasted-image_hu_ed17995bda270cb8.png 480w, /img/1793630117026-pasted-image_hu_b99f028d944e8bce.png 768w, /img/1793630117026-pasted-image_hu_339b3dcf9b18cd44.png 1200w, /img/1793630117026-pasted-image_hu_2ede2fac6d55a111.png 1600w, /img/1793630117026-pasted-image_hu_8cc5b49b25eb248d.png 2000w, /img/1793630117026-pasted-image.png 2048w"
          sizes="(max-width: 768px) 100vw, 700px"
          alt="Foundation&rsquo;s March 2022 post on X saying customer data is deleted 60 days after an order ships"
          
          width="2048" height="1126"
          
          
          loading="lazy"
          >
      </picture>
    
  



</p>
<p>Two more gaps remain. Orders on Foundation&rsquo;s Shopify store since May 2026 may also be exposed, because its automated deletion tools were still in development. And according to AMBCrypto&rsquo;s summary of the update, more than 5,000 recipients were not in either customer database, which suggests the attackers also used data from earlier leaks elsewhere.</p>
<p>
















  
  
  
    
    
    

    
    

    
      
      
      
      
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
      
      

      <picture>
        <source srcset="/img/1793630120753-pasted-image_hu_93a7fdafb4141c26.webp 480w, /img/1793630120753-pasted-image_hu_2c00e7c5ac2d0e69.webp 768w, /img/1793630120753-pasted-image_hu_c996f39ea6ac07b1.webp 1200w, /img/1793630120753-pasted-image_hu_728e9618f9249cbe.webp 1600w, /img/1793630120753-pasted-image_hu_13051a659a5e8825.webp 2000w, /img/1793630120753-pasted-image_hu_d0a2c227f3c47579.webp 2048w"
                sizes="(max-width: 768px) 100vw, 700px" type="image/webp">
        <img src="/img/1793630120753-pasted-image.png"
          srcset="/img/1793630120753-pasted-image_hu_2b8dde2015fdae82.png 480w, /img/1793630120753-pasted-image_hu_17c3d01225d93161.png 768w, /img/1793630120753-pasted-image_hu_a058a48f40b44814.png 1200w, /img/1793630120753-pasted-image_hu_ebcb20a723338940.png 1600w, /img/1793630120753-pasted-image_hu_35e4b6f458dda6bb.png 2000w, /img/1793630120753-pasted-image.png 2048w"
          sizes="(max-width: 768px) 100vw, 700px"
          alt="placed after the paragraph on the remaining gaps"
          
          width="2048" height="1143"
          
          
          loading="lazy"
          >
      </picture>
    
  



</p>
<h3 id="how-does-the-keystone-breach-compare">How does the Keystone breach compare?</h3>
<p>Keystone, another hardware wallet maker, disclosed its own breach on October 24. The entry points differ, but both deletion promises failed in the same place: in copies and tools around the main database. Hardware wallet makers hold the same retail data as any online store.</p>
<table style="min-width: 75px;"><tbody><tr><td colspan="1" rowspan="1"></td><td colspan="1" rowspan="1"><strong>Foundation</strong></td><td colspan="1" rowspan="1"><strong>Keystone</strong></td></tr><tr><td colspan="1" rowspan="1">Disclosed</td><td colspan="1" rowspan="1">October 26, 2026</td><td colspan="1" rowspan="1">October 24, 2026</td></tr><tr><td colspan="1" rowspan="1">Entry point</td><td colspan="1" rowspan="1">Sending credentials and a self-hosted app (under investigation)</td><td colspan="1" rowspan="1">Flaw in a third-party tool on its Shopify store</td></tr><tr><td colspan="1" rowspan="1">Data exposed</td><td colspan="1" rowspan="1">Names, contact details, addresses, past orders</td><td colspan="1" rowspan="1">25,964 buyer records (2024 to 2026) and the device authentication key</td></tr><tr><td colspan="1" rowspan="1">Deletion promise</td><td colspan="1" rowspan="1">60 days after shipping</td><td colspan="1" rowspan="1">180 days after the order</td></tr><tr><td colspan="1" rowspan="1">What failed</td><td colspan="1" rowspan="1">Database migrations kept copies of deleted records</td><td colspan="1" rowspan="1">Automated deletion tasks failed unnoticed</td></tr><tr><td colspan="1" rowspan="1">Response so far</td><td colspan="1" rowspan="1">Keys revoked, fake site down, report pending</td><td colspan="1" rowspan="1">Retention cut to 90 days, 18,835 units with the old key scrapped</td></tr></tbody></table>
<h2 id="indicators">Indicators</h2>
<p>Indicators from the Foundation campaign, defanged, as of November 2, 2026.</p>
<table style="min-width: 75px;"><tbody><tr><td colspan="1" rowspan="1"></td><td colspan="1" rowspan="1"><strong>Foundation</strong></td><td colspan="1" rowspan="1"><strong>Keystone</strong></td></tr><tr><td colspan="1" rowspan="1">Disclosed</td><td colspan="1" rowspan="1">October 26, 2026</td><td colspan="1" rowspan="1">October 24, 2026</td></tr><tr><td colspan="1" rowspan="1">Entry point</td><td colspan="1" rowspan="1">Sending credentials and a self-hosted app (under investigation)</td><td colspan="1" rowspan="1">Flaw in a third-party tool on its Shopify store</td></tr><tr><td colspan="1" rowspan="1">Data exposed</td><td colspan="1" rowspan="1">Names, contact details, addresses, past orders</td><td colspan="1" rowspan="1">25,964 buyer records (2024 to 2026) and the device authentication key</td></tr><tr><td colspan="1" rowspan="1">Deletion promise</td><td colspan="1" rowspan="1">60 days after shipping</td><td colspan="1" rowspan="1">180 days after the order</td></tr><tr><td colspan="1" rowspan="1">What failed</td><td colspan="1" rowspan="1">Database migrations kept copies of deleted records</td><td colspan="1" rowspan="1">Automated deletion tasks failed unnoticed</td></tr><tr><td colspan="1" rowspan="1">Response so far</td><td colspan="1" rowspan="1">Keys revoked, fake site down, report pending</td><td colspan="1" rowspan="1">Retention cut to 90 days, 18,835 units with the old key scrapped</td></tr></tbody></table>
<h2 id="how-to-protect-yourself-and-your-customers">How to protect yourself and your customers</h2>
<h3 id="for-passport-owners">For Passport owners</h3>
<ul>
<li>Treat any recall, replacement or &ldquo;funds at risk&rdquo; email as fake. A hardware wallet maker never needs your recovery phrase.</li>
<li>Check notices by typing <a href="http://foundation.xyz" rel="nofollow">foundation.xyz</a> yourself, and update firmware only through the Envoy app.</li>
<li>If you entered your recovery phrase anywhere, move your funds to a new wallet created on a trusted device.</li>
<li>Assume your address may be known, and distrust unexpected letters or visits about your wallet.</li>
</ul>
<h3 id="for-hardware-wallet-makers-and-other-companies-that-ship-to-crypto-holders">For hardware wallet makers and other companies that ship to crypto holders</h3>
<ul>
<li>Verify deletion in every copy: migration tables, backups, support inboxes and marketing tools, not only the main store.</li>
<li>Limit and rotate API keys for email and DNS services, and alert on unusual sending volume.</li>
<li>From the day you disclose an incident, monitor lookalike domains and fake support sites that use your name, and have takedown requests ready.</li>
</ul>
<p>PhishFort detects lookalike domains and fake sites that impersonate crypto brands, has analysts validate them and takes them down at the source. PhishFort has a 99%+ takedown success rate over the last year across its clients. <a href="https://phishfort.com/solutions/crypto-scamming-web3/" target="_blank" rel="noopener">See how PhishFort protects crypto brands from impersonation</a>.</p>
]]></content:encoded><category>Crypto</category><category>phishing</category><category>security</category><category>Foundation Passport</category><category>Passport hardware wallet</category><category>hardware wallet phishing</category><category>fake recall email</category><category>customer data breach</category><category>data retention</category><category>Keystone</category><category>Envoy</category><category>recovery phrase</category><category>wrench attacks</category></item></channel></rss>