Skip to content

Independent cybersecurity briefing

Latest

RSS
Breaches, bounties, zero-days, and AI.

Data Breaches

A suspected implant in a Trezor Safe 5 turns the seed into a radio leak

Trezor says a customer who bought from reseller CryptoBilis reported an extra board that can send the recovery phrase over a mobile network. Buyers since March 2026 are told to move funds.

By ZeroDay Times Desk3 min read

Story card “SEED LEAK” for Trezor, threat-spotlight view, [ BREACH ] badge, and the ZeroDay Times mark.

A hardware wallet is supposed to keep the recovery phrase offline. Trezor says it has received credible reports that one of its Safe 5 devices, sold through the Southeast Asian reseller CryptoBilis, may have been fitted with an extra circuit board that can send that phrase out over a mobile network. The company has not yet examined the device itself. The public instruction is already clear: treat the purchase path as compromised until proven otherwise.

BleepingComputer reported the warning on October 30, 2026. The Hacker News carried a parallel account the same day. Both rest on Trezor’s own post. The company is telling anyone who bought a Trezor from CryptoBilis since March 2026 to move funds to a new wallet and to generate a new recovery phrase. That advice does not wait for a teardown photo. It assumes the seed on the old device may already have left the case.

What the report claims, and what it does not

The customer account, as retold in the public coverage, describes hardware that does not belong in a stock Safe 5: an added board with a cellular radio path. If that description holds, the failure is not a firmware CVE and not a phishing page. It is a supply-chain implant at the point of sale. The phrase never needs to touch a laptop. The radio does the exfiltration.

Trezor has said it has not completed its own examination. That matters for attribution and for product liability language. It matters less for the person who already typed twenty-four words into that device. A suspected implant is enough reason to rotate. Waiting for a lab photo while coins sit on the old seed is a choice, not a control.

This desk will not describe how such a board would be wired, how a phrase would be captured, or how to build one. Those details help the wrong reader. Defenders need the commercial fact: a branded box from an unofficial or lightly vetted reseller is not the same object as a device that left the manufacturer’s own channel untouched.

Why a reseller is the attack surface

Hardware wallets are sold as an answer to malware on the computer. That answer collapses if the device itself is altered between the factory and the buyer. A reseller with regional reach is a high-value insert point. One tampered unit can empty one person’s holdings. A pattern of tampered units turns into a campaign. The public reporting so far points at a single reseller name and a window that starts in March 2026. Trezor is treating that window as the recall boundary for CryptoBilis purchases.

Official channels, sealed packaging, and physical inspection habits exist for this reason. They are tedious. They are cheaper than moving a life savings after the phrase has already been radioed out. Corporate treasuries that keep cold keys on consumer hardware should treat procurement the way they treat signing-desk laptops: named vendor, sealed delivery, and a second person who checks the device before the first seed is written.

What holders and programs should do now

If you bought from CryptoBilis in the window Trezor named, follow the company’s instruction without editing it for comfort. Create a new wallet on a device from a channel you trust. Move the funds. Retire the old phrase. Do not reuse it for a “temporary” wallet while you wait for more news.

If you bought elsewhere, do not treat this as a free pass for every grey-market listing. The lesson is the path, not only the logo on one shop. Prefer the manufacturer’s store or a reseller the manufacturer lists. Inspect the device against the vendor’s published teardown or authenticity guidance before generating a seed. A board that should not be there is a stop, not a curiosity.

Organizations that custody crypto for customers should write the reseller rule into policy, not into a Slack tip. Inventory which devices were bought where. Require dual control when a seed is generated. Assume that a single compromised unit can drain an account that never saw malware. The Binance signing-desk theft earlier the same day is a software-and-process story. This one is a hardware story. Both end the same way for the holder: the coins leave, and the brand on the box does not bring them back.

This briefing relies on public reporting by BleepingComputer and The Hacker News, and on Trezor’s published warning. It does not describe implant construction or exfiltration steps.

Corrections and tips:[email protected]