<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>WalletInsights: hardware wallet security incidents</title>
    <link>https://walletinsights.io/en/security-incidents/</link>
    <atom:link href="https://walletinsights.io/en/security-incidents/feed.xml" rel="self" type="application/rss+xml" />
    <description>Sourced record of hardware wallet vulnerabilities, chip attacks, tampered devices and vendor data breaches, with severity, fix status and reported losses.</description>
    <language>en</language>
    <lastBuildDate>Fri, 30 Oct 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Suspected implant in a Trezor Safe 5 sold by CryptoBilis</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-cryptobilis-implant-report-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-cryptobilis-implant-report-2026/</guid>
      <pubDate>Fri, 30 Oct 2026 12:00:00 GMT</pubDate>
      <category>Supply chain</category>
      <description>One reported unit, not yet examined by Trezor at the time of writing. The report concerns how a device reached a buyer, not the device design.</description>
    </item>
    <item>
      <title>Phishing emails sent from Foundation's own systems to Passport owners</title>
      <link>https://walletinsights.io/en/security-incidents/foundation-passport-phishing-backend-breach-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/foundation-passport-phishing-backend-breach-2026/</guid>
      <pubDate>Mon, 26 Oct 2026 12:00:00 GMT</pubDate>
      <category>Vendor infrastructure compromise</category>
      <description>Thousands of Passport customers and other contacts received convincing phishing from Foundation's own domains, and about 5,600 addresses and 5,200 phone numbers are treated as exposed. Foundation states devices and funds on Passport were not compromised.</description>
    </item>
    <item>
      <title>Keystone website breach exposed buyer data and the device authentication key</title>
      <link>https://walletinsights.io/en/security-incidents/keystone-website-breach-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/keystone-website-breach-2026/</guid>
      <pubDate>Tue, 20 Oct 2026 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Buyers' names, addresses and order details are in attackers' hands, which invites targeted phishing. The stolen authentication key means the online authenticity check can no longer rule out counterfeits made with the old key.</description>
    </item>
    <item>
      <title>Hijacked NGRAVE push notifications lead to $2.56M phishing theft</title>
      <link>https://walletinsights.io/en/security-incidents/ngrave-liquid-push-notification-phishing-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ngrave-liquid-push-notification-phishing-2026/</guid>
      <pubDate>Mon, 19 Oct 2026 12:00:00 GMT</pubDate>
      <category>Vendor infrastructure compromise</category>
      <description>LIQUID users who followed the fake alert and entered their recovery phrase or Perfect Key lost funds, about $2.56 million by NGRAVE's count; app usage data of other users was also exposed. NGRAVE states its ZERO devices and their keys were not compromised.</description>
    </item>
    <item>
      <title>Hardware implants in Ledger devices sold by CryptoBilis</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-cryptobilis-hardware-implant-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-cryptobilis-hardware-implant-2026/</guid>
      <pubDate>Tue, 13 Oct 2026 12:00:00 GMT</pubDate>
      <category>Supply chain</category>
      <description>Buyers of tampered units lost their recovery phrases at setup and, with them, their funds. The device design is not affected; the risk is in how the devices reached buyers.</description>
    </item>
    <item>
      <title>Ledger Ethereum app clear-signing bypass hid all but one operation of a large batch</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-ethereum-app-clear-signing-array-truncation-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-ethereum-app-clear-signing-array-truncation-2026/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Users of Ledger Ethereum app 1.19.0 to 1.22.2 signing through a compromised host could approve a batch of more than 255 operations while seeing only one. Ledger describes exploitation as difficult and fixed the flaw in Ethereum app 1.22.3.</description>
    </item>
    <item>
      <title>Ledger Ethereum app swap flow could sign a token approval in place of a payment</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-ethereum-app-swap-approval-substitution-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-ethereum-app-swap-approval-substitution-2026/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Users swapping tokens through Ledger's Exchange app with Ethereum app 1.20.0 to 1.22.2 could, via a hostile swap provider, sign a token approval for the agreed amount to the swap's deposit address instead of a payment. Ledger states the permission moves no funds by itself and found no evidence of exploitation.</description>
    </item>
    <item>
      <title>Ledger Secure SDK flaw let a host change transaction details after on-screen review</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-secure-sdk-review-signature-desync-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-secure-sdk-review-signature-desync-2026/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Users of Ledger device apps built on Secure SDK releases from August 2025 through v26.6.0 could, if a compromised host or web page controlled the connection, approve an operation shown correctly on screen and sign different parameters. Ledger states it has no evidence of exploitation against users.</description>
    </item>
    <item>
      <title>BitBox02 firmware flaws could let attackers install malicious firmware</title>
      <link>https://walletinsights.io/en/security-incidents/bitbox02-dixence-firmware-flaws-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/bitbox02-dixence-firmware-flaws-2026/</guid>
      <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>BitBox02 owners on older firmware could have malicious firmware installed after being phished into using a fake app, and un-set-up Multi devices were exposed to a malicious computer. BitBox reports no exploitation or stolen funds and states seeds were not affected.</description>
    </item>
    <item>
      <title>SafePal order-tracking flaw exposes data of 39,798 customers</title>
      <link>https://walletinsights.io/en/security-incidents/safepal-customer-order-data-breach-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/safepal-customer-order-data-breach-2026/</guid>
      <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Names, contact details and shipping addresses of about 39,798 SafePal customers were exposed, and some were then targeted with phishing. SafePal states wallets and funds were not compromised by the breach itself.</description>
    </item>
    <item>
      <title>Breach at shipping provider ShipMonk exposes data of up to 80,689 Trezor customers</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-shipmonk-customer-data-breach-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-shipmonk-customer-data-breach-2026/</guid>
      <pubDate>Thu, 13 Aug 2026 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Names, contact details and shipping addresses of up to 80,689 Trezor customers were exposed through ShipMonk, raising the risk of targeted phishing. Trezor states its systems and devices were not affected.</description>
    </item>
    <item>
      <title>Bitkey app used a non-cryptographic random generator for contact enrollment</title>
      <link>https://walletinsights.io/en/security-incidents/bitkey-relationship-enrollment-weak-randomness-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/bitkey-relationship-enrollment-weak-randomness-2026/</guid>
      <pubDate>Sun, 02 Aug 2026 12:00:00 GMT</pubDate>
      <category>Software vulnerability</category>
      <description>Second-generation Bitkey users who enrolled Recovery Contacts or inheritance beneficiaries used secrets generated with a predictable random generator. Bitkey states the bug could not on its own give access to funds and that no customer was exploited.</description>
    </item>
    <item>
      <title>COLDCARD firmware generated weak seeds</title>
      <link>https://walletinsights.io/en/security-incidents/coldcard-weak-seed-generation-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/coldcard-weak-seed-generation-2026/</guid>
      <pubDate>Thu, 30 Jul 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Funds on seeds generated with the affected firmware can be found and swept remotely. Current firmware is fixed, but the risk remains for funds still held on old seeds.</description>
    </item>
    <item>
      <title>Laser fault injection bypasses Tangem card access codes</title>
      <link>https://walletinsights.io/en/security-incidents/tangem-laser-fault-injection-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/tangem-laser-fault-injection-2026/</guid>
      <pubDate>Thu, 09 Jul 2026 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>Someone who steals a card and has laboratory equipment can sign transactions without the access code. Cards already sold cannot be patched.</description>
    </item>
    <item>
      <title>USB SDK flaw allowed code execution on an unlocked Keystone 3 Pro</title>
      <link>https://walletinsights.io/en/security-incidents/keystone-3-pro-usb-sdk-code-execution-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/keystone-3-pro-usb-sdk-code-execution-2026/</guid>
      <pubDate>Fri, 03 Jul 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Someone holding a Keystone 3 Pro on firmware older than 2.4.0, knowing its PIN and approving a USB connection on it could run code on its microcontroller; ANZEN says this led to the recovery phrase. Keystone reports no exploitation.</description>
    </item>
    <item>
      <title>Ledger Monero app exposed Keccak state, letting a compromised host recover spend keys</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-monero-app-keccak-state-key-recovery-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-monero-app-keccak-state-key-recovery-2026/</guid>
      <pubDate>Thu, 04 Jun 2026 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Monero holders using a Ledger Monero app older than 2.1.4 on a compromised computer could have their secret view and spend keys extracted without any prompt on the device while the app was open. Ledger states the issue is fixed in Monero app 2.1.4 and that the prerequisites considerably limit practical exploitability.</description>
    </item>
    <item>
      <title>Laser fault injection bypasses firmware checks on Trezor Safe 7's TROPIC01 chip</title>
      <link>https://walletinsights.io/en/security-incidents/tropic01-laser-fault-injection-trezor-safe-7-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/tropic01-laser-fault-injection-trezor-safe-7-2026/</guid>
      <pubDate>Wed, 03 Jun 2026 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>A lab attacker holding a Trezor Safe 7 can run arbitrary firmware on its TROPIC01 secure element and, per Tropic Square and Ledger, compromise its MAC-and-Destroy protection. Trezor states this alone does not expose the PIN, funds or wallet backup and that no user action is needed.</description>
    </item>
    <item>
      <title>Fake Ledger Live app in Apple's App Store</title>
      <link>https://walletinsights.io/en/security-incidents/fake-ledger-live-apple-app-store-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/fake-ledger-live-apple-app-store-2026/</guid>
      <pubDate>Tue, 14 Apr 2026 12:00:00 GMT</pubDate>
      <category>Targeted phishing</category>
      <description>Mac users who installed the fake app and entered their recovery phrase lost about $9.5 million in total, according to ZachXBT. Ledger states it never asks for the recovery phrase.</description>
    </item>
    <item>
      <title>Breach at e-commerce partner Global-e exposes Ledger.com customers' order data</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-global-e-order-data-breach-2026/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-global-e-order-data-breach-2026/</guid>
      <pubDate>Mon, 05 Jan 2026 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Names, contact details, postal addresses and order details of an undisclosed number of Ledger.com customers who bought through Global-e were exposed, raising the risk of targeted phishing. Ledger states its systems, devices and customers' crypto assets were not affected.</description>
    </item>
    <item>
      <title>Blockstream Jade firmware bug let a malicious host corrupt device memory</title>
      <link>https://walletinsights.io/en/security-incidents/blockstream-jade-register-descriptor-memory-corruption-2025/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/blockstream-jade-register-descriptor-memory-corruption-2025/</guid>
      <pubDate>Fri, 05 Dec 2025 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>A Jade on firmware 1.0.24–1.0.36, unlocked and connected to a compromised computer or phone or to a malicious web page, could be crashed or made to run limited code. Blockstream states users of its own app on a clean device were not at immediate risk and no users are known to be affected.</description>
    </item>
    <item>
      <title>Ledger Donjon bypasses Trezor Safe 3 supply-chain protections</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-donjon-trezor-safe-3-glitching-2025/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-donjon-trezor-safe-3-glitching-2025/</guid>
      <pubDate>Wed, 12 Mar 2025 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>An attacker with lab equipment could turn a Safe 3 into a device running malicious firmware that still passes authenticity checks, then sell it to a victim. Devices bought from official sources and the Safe 5 are not affected, according to Trezor.</description>
    </item>
    <item>
      <title>Ledger MCU firmware update flaw could permanently brick Nano X, Flex and Stax</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-mcu-update-reset-handler-bricking-2025/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-mcu-update-reset-handler-bricking-2025/</guid>
      <pubDate>Fri, 10 Jan 2025 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>A Ledger Nano X, Flex or Stax on firmware older than 2.4.2, 1.2.2 or 1.6.2 respectively could be made permanently unusable through a crafted MCU firmware update. Ledger states the impact is limited to device operability and funds were never at risk.</description>
    </item>
    <item>
      <title>Tangem app logged seed-phrase private keys sent to support</title>
      <link>https://walletinsights.io/en/security-incidents/tangem-app-seed-phrase-logging-bug-2024/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/tangem-app-seed-phrase-logging-bug-2024/</guid>
      <pubDate>Mon, 30 Dec 2024 12:00:00 GMT</pubDate>
      <category>Software vulnerability</category>
      <description>Users who activated a seed-phrase wallet and contacted Tangem support through the app within 7 days had their private key included in the logs sent to support. Tangem states fewer than 0.1% of users were affected, the logs were deleted and no funds were lost.</description>
    </item>
    <item>
      <title>EUCLEAK side channel in Infineon ECDSA library reaches Trezor Safe 3 and Safe 5 chip</title>
      <link>https://walletinsights.io/en/security-incidents/eucleak-infineon-side-channel-trezor-safe-2024/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/eucleak-infineon-side-channel-trezor-safe-2024/</guid>
      <pubDate>Tue, 03 Sep 2024 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>An attacker with physical access and laboratory equipment could, per NinjaLab, extract ECDSA keys from the OPTIGA Trust M chip used in the Trezor Safe 3 and Safe 5. Trezor states the recovery seed and funds are not at risk because that cryptography does not protect the wallet backup.</description>
    </item>
    <item>
      <title>Trezor support portal breach exposes 66,000 contacts</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-support-portal-data-breach-2024/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-support-portal-data-breach-2024/</guid>
      <pubDate>Wed, 17 Jan 2024 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Names and email addresses of up to 66,000 support contacts were exposed, and some then received emails asking for their recovery seed. Trezor states no funds were compromised and the devices were unaffected.</description>
    </item>
    <item>
      <title>Ledger Connect Kit npm supply-chain attack</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-connect-kit-supply-chain-attack-2023/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-connect-kit-supply-chain-attack-2023/</guid>
      <pubDate>Thu, 14 Dec 2023 12:00:00 GMT</pubDate>
      <category>Supply chain</category>
      <description>Users of dApps that loaded the compromised library, with any wallet, could be drained by approving malicious transactions during a window of under two hours. Ledger devices and Ledger Live were not compromised, according to Ledger.</description>
    </item>
    <item>
      <title>Fake Ledger Live app in the Microsoft Store</title>
      <link>https://walletinsights.io/en/security-incidents/fake-ledger-live-microsoft-store-2023/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/fake-ledger-live-microsoft-store-2023/</guid>
      <pubDate>Sun, 05 Nov 2023 12:00:00 GMT</pubDate>
      <category>Targeted phishing</category>
      <description>Windows users who installed the fake app from the Microsoft Store lost about $768,000–$770,000 in total, according to press reports citing ZachXBT.</description>
    </item>
    <item>
      <title>Counterfeit Trezor Model T with modified bootloader and preset seeds</title>
      <link>https://walletinsights.io/en/security-incidents/counterfeit-trezor-model-t-preset-seeds-2023/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/counterfeit-trezor-model-t-preset-seeds-2023/</guid>
      <pubDate>Wed, 10 May 2023 12:00:00 GMT</pubDate>
      <category>Supply chain</category>
      <description>Anyone who set up a wallet on such a counterfeit used a seed the attacker already knew. Owners of genuine devices bought through official channels are not affected.</description>
    </item>
    <item>
      <title>OneKey Mini and Touch seed extraction via secure element bus</title>
      <link>https://walletinsights.io/en/security-incidents/onekey-mini-secure-element-bus-interception-2023/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/onekey-mini-secure-element-bus-interception-2023/</guid>
      <pubDate>Fri, 10 Feb 2023 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>An attacker with an affected device in hand and lab equipment could extract the seed phrase. OneKey states the issue is patched and no users were affected.</description>
    </item>
    <item>
      <title>Trezor's Mailchimp newsletter used to send fake Trezor Suite</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-mailchimp-newsletter-phishing-2022/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-mailchimp-newsletter-phishing-2022/</guid>
      <pubDate>Sun, 03 Apr 2022 12:00:00 GMT</pubDate>
      <category>Vendor infrastructure compromise</category>
      <description>Owners who installed the fake Trezor Suite and entered their recovery phrase gave attackers control of their funds. Subscribers' email addresses and, in some cases, names and IP addresses were exposed, according to Trezor, which invites further targeted phishing.</description>
    </item>
    <item>
      <title>Fake Ledger Nano X devices mailed to data breach victims</title>
      <link>https://walletinsights.io/en/security-incidents/fake-ledger-devices-mailed-to-breach-victims-2021/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/fake-ledger-devices-mailed-to-breach-victims-2021/</guid>
      <pubDate>Wed, 16 Jun 2021 12:00:00 GMT</pubDate>
      <category>Targeted phishing</category>
      <description>Owners whose addresses were in the leaked database could receive a convincing counterfeit built to collect their recovery phrase. Anyone who followed the instructions would hand attackers control of their funds.</description>
    </item>
    <item>
      <title>Kraken bypasses SafePal S1 tamper detection and downgrades its firmware</title>
      <link>https://walletinsights.io/en/security-incidents/kraken-safepal-s1-tamper-detection-bypass-2021/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/kraken-safepal-s1-tamper-detection-bypass-2021/</guid>
      <pubDate>Tue, 16 Feb 2021 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>Someone with physical access could open an S1 without triggering its tamper response and roll back its firmware, but Kraken did not reach keys or funds. SafePal states the findings are not exploitable and patched the downgrade in firmware 1.0.24.</description>
    </item>
    <item>
      <title>Coldcard registered multisig wallets without checking it was a cosigner</title>
      <link>https://walletinsights.io/en/security-incidents/coldcard-multisig-xpub-substitution-2021/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/coldcard-multisig-xpub-substitution-2021/</guid>
      <pubDate>Tue, 09 Feb 2021 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Users who registered a multisig wallet on a Coldcard on firmware 3.1.9 or earlier through a compromised computer could end up with a wallet the attacker controls or can hold to ransom. Coinkite disputes that this is a remote attack, since it requires a compromised computer at wallet creation.</description>
    </item>
    <item>
      <title>Coldcard testnet mode could be used to sign a real bitcoin transaction</title>
      <link>https://walletinsights.io/en/security-incidents/coldcard-testnet-isolation-bypass-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/coldcard-testnet-isolation-bypass-2020/</guid>
      <pubDate>Tue, 24 Nov 2020 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>A Coldcard owner on firmware 3.1.9 or earlier persuaded to switch the device to testnet and sign an attacker-supplied transaction could lose real bitcoin. Coinkite considers the attack unrealistic because switching to testnet requires explicit action on the device.</description>
    </item>
    <item>
      <title>Ledger customer database breach</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-customer-database-breach-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-customer-database-breach-2020/</guid>
      <pubDate>Wed, 29 Jul 2020 12:00:00 GMT</pubDate>
      <category>Customer data breach</category>
      <description>Names, postal addresses, phone numbers and email addresses of Ledger buyers became public, which identifies them as crypto holders. No device or seed compromise was reported, but the data was later used for phishing, including fake devices sent by mail.</description>
    </item>
    <item>
      <title>Ledger Nano X debug interface enabled supply-chain attacks (Kraken)</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-nano-x-debug-interface-supply-chain-attacks-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-nano-x-debug-interface-supply-chain-attacks-2020/</guid>
      <pubDate>Wed, 08 Jul 2020 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>A Nano X tampered with before first use could act as a keyboard on the owner's computer or hide transactions from the screen. Ledger states the Secure Element and user secrets were not affected and that firmware 1.2.4-2 fixes the issue.</description>
    </item>
    <item>
      <title>Ledger Bitcoin app SegWit fee overpayment vulnerability</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-bitcoin-app-segwit-fee-overpayment-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-bitcoin-app-segwit-fee-overpayment-2020/</guid>
      <pubDate>Wed, 03 Jun 2020 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Users of the Ledger Bitcoin app and SegWit-capable forks before version 1.4.0 could lose funds to inflated fees if their computer's wallet software was compromised and they signed the same transaction twice. Ledger states the issue is fixed in Bitcoin app 1.4.0.</description>
    </item>
    <item>
      <title>SegWit double-signing flaw could make Trezor users pay a huge fee</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-segwit-double-signing-fee-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-segwit-double-signing-fee-2020/</guid>
      <pubDate>Wed, 03 Jun 2020 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>A Trezor user signing on a compromised computer could be led to sign twice and lose most of the transaction's inputs to fees. Trezor lists the issue as fixed in Trezor One 1.9.1 and Model T 2.3.1.</description>
    </item>
    <item>
      <title>Ledger Monero app spend key extraction (CVE-2020-6861)</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-monero-app-spend-key-extraction-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-monero-app-spend-key-extraction-2020/</guid>
      <pubDate>Sat, 25 Apr 2020 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Monero holders using Ledger Monero app versions before 1.5.1 with a malicious or compromised Monero client could have their spend key extracted without any sign on the device. Ledger states the issue is fixed in Monero app 1.5.1.</description>
    </item>
    <item>
      <title>Kraken finds CoolWallet S app leaked seed, PIN and pairing password</title>
      <link>https://walletinsights.io/en/security-incidents/kraken-coolwallet-s-app-seed-pin-exposure-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/kraken-coolwallet-s-app-seed-pin-exposure-2020/</guid>
      <pubDate>Fri, 03 Apr 2020 12:00:00 GMT</pubDate>
      <category>Software vulnerability</category>
      <description>CoolWallet S owners whose phone was stolen or infected could have their seed, PIN and pairing password exposed by the Android app. CoolWallet states the risk was limited and that the logging, screen-capture and bypass issues were fixed in its next app release.</description>
    </item>
    <item>
      <title>Kraken extracts Trezor One and Model T seeds by voltage glitching</title>
      <link>https://walletinsights.io/en/security-incidents/kraken-trezor-voltage-glitch-seed-extraction-2020/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/kraken-trezor-voltage-glitch-seed-extraction-2020/</guid>
      <pubDate>Fri, 31 Jan 2020 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>Someone holding a Trezor One or Model T without a passphrase could recover its seed with specialised equipment in about 15 minutes. A device protected by a BIP39 passphrase is not exposed, according to both Kraken and Trezor.</description>
    </item>
    <item>
      <title>Ledger Donjon extracts Trezor seeds in minutes with physical access</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-donjon-trezor-seed-extraction-2019/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-donjon-trezor-seed-extraction-2019/</guid>
      <pubDate>Mon, 01 Jul 2019 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>Anyone holding a Trezor One or Model T without a strong passphrase could, according to Ledger, extract its seed in minutes with inexpensive equipment. Trezor states a passphrase fully mitigates the attack and disputes that it was disclosed to the company.</description>
    </item>
    <item>
      <title>Ledger Donjon dumps encrypted keys from the Ellipal EC01 via debug ports</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-donjon-ellipal-ec01-flash-dump-2019/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-donjon-ellipal-ec01-flash-dump-2019/</guid>
      <pubDate>Tue, 25 Jun 2019 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>Someone with physical access to an EC01 and lab tools could dump its encrypted keys and, if the password was weak, brute-force them, or backdoor the device. Ellipal states that no seeds were extracted and that firmware v2.0 and the Titan redesign address the findings.</description>
    </item>
    <item>
      <title>Trezor One 1.8.0 fixes glitching attacks that read the seed from memory</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-one-glitching-memory-readout-fixes-2019/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-one-glitching-memory-readout-fixes-2019/</guid>
      <pubDate>Wed, 06 Mar 2019 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>An attacker with physical access to a Trezor One on firmware older than 1.8.0 could read the seed from memory unless a passphrase was set. Trezor fixed them in Trezor One firmware 1.8.0; the Model T was not directly affected and received the same protections in 2.1.0.</description>
    </item>
    <item>
      <title>wallet.fail at 35C3: Ledger Nano S MCU firmware and Ledger Blue PIN side channel</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-wallet-fail-35c3-nano-s-blue-attacks-2018/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-wallet-fail-35c3-nano-s-blue-attacks-2018/</guid>
      <pubDate>Thu, 27 Dec 2018 12:00:00 GMT</pubDate>
      <category>Hardware attack</category>
      <description>An attacker with physical access to a Nano S, combined with malware on the owner's computer, or one positioned within close radio range of a Ledger Blue during PIN entry, could undermine the device's protections in lab conditions. Ledger states the findings showed no practical vulnerability and that no seed or PIN was extracted from a stolen device.</description>
    </item>
    <item>
      <title>Ledger Nano S MCU firmware verification bypass</title>
      <link>https://walletinsights.io/en/security-incidents/ledger-nano-s-mcu-verification-bypass-2018/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/ledger-nano-s-mcu-verification-bypass-2018/</guid>
      <pubDate>Tue, 20 Mar 2018 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>An attacker who handled a Nano S on firmware 1.3.1 or earlier, before delivery or after setup, could install firmware that controlled or captured the recovery seed. Devices on firmware 1.4.1 are not affected, according to Ledger.</description>
    </item>
    <item>
      <title>Trezor One firmware left seed in RAM, readable with physical access</title>
      <link>https://walletinsights.io/en/security-incidents/trezor-one-sram-seed-extraction-2017/</link>
      <guid isPermaLink="true">https://walletinsights.io/en/security-incidents/trezor-one-sram-seed-extraction-2017/</guid>
      <pubDate>Thu, 17 Aug 2017 12:00:00 GMT</pubDate>
      <category>Firmware vulnerability</category>
      <description>Someone with physical access to an opened Trezor One running firmware older than 1.5.2 could read its seed and PIN from RAM; passphrase-protected wallets were not exposed, according to the researcher's write-up. Trezor states the issue was fixed in 2017.</description>
    </item>
  </channel>
</rss>
