AEGLIX News
Trezor has verified that three Safe 5 hardware wallets distributed by the Southeast Asian vendor CryptoBilis were embedded with malicious hardware implants engineered to harvest wallet recovery phrases and send them to threat actors via cellular connections. Each of the three tainted units was bought from CryptoBilis during the window from August 20 through September 23, 2026. After analyzing the first device in its lab, Trezor used owner‑supplied photographs to pinpoint two more compromised wallets. The firm also reviewed devices sourced from other regional resellers and uncovered no signs of tampering.
In the wake of Trezor's October alert, 48 CryptoBilis buyers have reached out to the company, submitting their devices for laboratory inspection or providing internal‑component photos for review. Trezor reports no evidence of implants in hardware from other resellers and no incidents of funds being stolen through the compromised Safe 5 units. By contrast, earlier hardware implants found in Ledger devices sold via CryptoBilis have been tied to actual cryptocurrency thefts. Prompted by these supply‑chain breaches, Trezor has shrunk its worldwide reseller network by roughly 80%.
The covert implant takes the form of an extra circuit board sandwiched between the Safe 5's main board and its display, enabling it to observe screen output without altering the device's genuine firmware or Secure Element. It is capable of recording recovery words and passphrases shown on the screen, encrypting that data, and dispatching it over a mobile network to a server under the attacker's control, retrying transmission whenever connectivity is absent.
On November 11 Trezor shipped firmware version 2.13.1, which adds safeguards that stop the implants from harvesting data on devices running the update. The patch cannot retroactively protect recovery phrases that may have already been captured before installation. Trezor is providing replacement units to any customer who bought a Trezor wallet from CryptoBilis since March 2026, even if their device has not been confirmed as compromised.
Report prepared 2026-11-13 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)