Trezor updates investigation into Safe 5 implant: only 3 devices via CryptoBilis channel, firmware 2.13.1 renders the implant ineffective
Hardware wallet maker Trezor updated its investigation results into the Trezor Safe 5 hardware implant incident on November 12. The company confirmed that the implants identified were limited to Safe 5 devices purchased through the distributor CryptoBilis between August 20, 2026 and September 23, 2026, including its Tokopedia and Shopee stores as well as direct purchases.
Among the devices examined, a total of 3 were confirmed affected (including one reported in October, which the laboratory inspected; the other two were confirmed through internal photos provided by users). None of the 3 device owners reported any loss of funds. No signs of implants were found in other distributor channels or other Trezor models.
Trezor released firmware 2.13.1 on November 11, which includes safeguards that can prevent the identified implant from capturing screen content, including mnemonic seed phrases and passphrases, making the current batch of implants ineffective. The company has reduced its distributor network by about 80% and imposed stricter supply-chain controls on remaining partners. The investigation is still ongoing.
The company recommends that users who purchased devices through CryptoBilis since March 2026 transfer their funds to a new wallet using a new seed phrase, and they may contact Trezor support to request a free device replacement.
Original source:
Title: Our CryptoBilis investigation: what we found and what we’ve changed
Publisher: Trezor
Publication date: 2026-11-12 (the page is marked Nov 11; the content is an update)
URL: trezor.io/blog/news/our-cryptobilis-investigation-what-we-found-and-what-weve-changed
Source type: official company announcement
Verification status: the full official blog post was actually read for this article, verified on 2026-11-12
Supporting content: supports the limited scope of the implant, the 3 confirmed devices, no loss of funds, the firmware 2.13.1 function, the reduction of the distributor network by about 80%, and the user recommendation
ABAB AI Insight
This incident is a physical tampering event in the supply chain, rather than a broad flaw in Trezor's own manufacturing or firmware. The implant is an additional circuit board placed between the main board and the screen; it only monitors and copies the screen content and then exfiltrates it over a mobile network, without modifying the device firmware or secure element. The scope is concentrated in a specific time window at a single distributor, indicating that the problem is more likely in the distribution or warehousing process.
The firmware update provides a software-level block against the identified type of implant, reducing the risk of future use. However, the company still recommends that users from the affected batch change their seed phrase and move their funds, because the update cannot undo the historical backups already captured by the implant. This reflects the irreversibility of physical access and screen information leakage in hardware wallet scenarios.
The sharp reduction in the distributor network and tighter controls show that the company is choosing to narrow authorized channels to reduce the future supply-chain attack surface, rather than relying only on device-side detection. In combination with a similar implant incident previously seen at Ledger through the same distributor channel, this highlights the critical role of third-party distributors in the hardware wallet security chain.
Key follow-up points include whether the investigation finds more devices, whether any funds loss is reported, and whether the company's specific audit and verification measures for remaining distributors are disclosed. On the user side, the risk difference between official channels and third-party purchases still needs to be distinguished.
ABAB News · Cognitive Law
When supply-chain risk in hardware wallets is concentrated in the distribution link, the affected scope can be defined by the purchase channel and time window.
Firmware can block subsequent capture by a known implant, but it cannot eliminate the historical risk of a seed phrase that has already been copied.