Back to Intelligence

Trezor Safe 5 Hardware Implants Sold via CryptoBilis: Supply-Chain Compromise Detection and Response Guide

SA
Security Arsenal Team
November 14, 2026
11 min read

Trezor has confirmed that three Safe 5 hardware wallets sold through Southeast Asian reseller CryptoBilis contained malicious hardware implants engineered to capture wallet recovery phrases and transmit them to attackers over cellular networks. Trezor has released a fix, but the confirmed compromise of physical devices in the distribution channel elevates this from a consumer fraud story to a genuine supply-chain security incident.

If your organization permits hardware wallets on corporate endpoints, holds treasury assets in self-custody, or has employees in Southeast Asia who purchased devices through third-party resellers, you need to treat this as an active incident-response scenario. A stolen recovery phrase is not a vulnerability that can be patched after the fact — it is full, irreversible custody of every asset derived from that seed. The attacker's window to drain funds is any time they choose.

Technical Analysis

What Happened

Cryptocurrency hardware wallet manufacturer Trezor confirmed that three Safe 5 devices sold by CryptoBilis, a reseller operating in Southeast Asia, were tampered with before reaching end users. The devices contained malicious hardware implants — physically modified internal components — designed to intercept the wallet recovery phrase (the 12/20/24-word seed) and exfiltrate it to attacker-controlled infrastructure over cellular networks.

The cellular exfiltration channel is the critical detail. Traditional hardware-wallet tampering attacks rely on the compromised device leaking secrets through the host computer it is connected to — which at least passes through a potentially monitored endpoint. A cellular-enabled implant bypasses the host entirely: the wallet itself phones home over mobile networks, invisible to any EDR, network monitor, or proxy your organization operates. There is no packet to capture on your wire.

Attack Chain (Defender's View)

  1. Supply-chain insertion: Devices in the distribution channel — at or downstream of the reseller — are opened and physically modified with an implant capable of reading the device's secure element interactions or display/processor bus during seed generation or backup.
  2. Seed capture: When the victim initializes the wallet or performs a recovery-phrase backup, the implant captures the seed words.
  3. Out-of-band exfiltration: The implant transmits the captured phrase over a cellular connection directly to the attacker. No host interaction, no USB data path, no observable network traffic on the victim's infrastructure.
  4. Delayed monetization: The attacker derives the victim's private keys and waits — often until the wallet balance justifies the risk of draining it. Victims may use a compromised device for months with no indication.

Affected Products

  • Product: Trezor Safe 5 hardware wallets
  • Distribution vector: Units sold by reseller CryptoBilis (Southeast Asia)
  • Confirmed scope: Three devices confirmed by Trezor. The unconfirmed population is the real concern — defenders should assume any Safe 5 purchased through unofficial or third-party channels in the region is suspect until verified.
  • CVE: No CVE has been assigned to this incident. This is a physical supply-chain compromise, not a software vulnerability, and CVSS scoring does not apply. Do not wait for a CVE entry to act.

Exploitation Status

This is confirmed in-the-wild compromise of physical devices — not theoretical. Trezor has publicly acknowledged the implanted units and released a fix incorporating device-authenticity verification to help users identify tampered hardware. Whether additional compromised units remain in circulation is unknown, which is precisely why verification of device provenance and integrity is now an operational requirement rather than a best practice.

Why Host-Based Detection Is Hard Here

Be honest with your stakeholders: the implant's cellular exfiltration does not traverse the corporate endpoint or network, so no Sigma rule will catch the theft itself. What endpoint telemetry can do is (a) identify where Trezor devices are in use so you can scope exposure, (b) flag devices sourced from untrusted channels, and (c) catch trojanized companion software (fake Trezor Suite installers), which historically rides alongside hardware-wallet targeting campaigns. The detections below are scoped accordingly — they are exposure-discovery and hygiene controls, not magic.

Detection & Response

Sigma Rules

YAML
---
title: Trezor Hardware Wallet USB Device Connected to Endpoint
id: 8f2c4a17-3b9e-4d51-a6c8-7e1f2b3d4c5a
status: experimental
description: Detects connection of a Trezor hardware wallet (USB VID 1209, SatoshiLabs) via USBSTOR registry artifacts. Used to scope hardware-wallet usage for supply-chain exposure assessment following confirmed Safe 5 implant incidents. High fidelity in environments where hardware wallets are not sanctioned.
references:
  - https://www.bleepingcomputer.com/news/cryptocurrency/trezor-confirms-crypto-stealing-implants-in-three-wallets-releases-fix/
  - https://attack.mitre.org/techniques/T1200/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1200
logsource:
  category: registry_set
  product: windows
detection:
  selection:
    TargetObject|contains:
      - 'Enum\USB\VID_1209'
      - 'Enum\USBSTOR\'
    Details|contains:
      - 'TREZOR'
      - 'SatoshiLabs'
      - 'Safe 5'
  condition: selection
falsepositives:
  - Legitimate Trezor use by sanctioned personnel (crypto treasury, security research)
level: medium
---
title: Trezor Suite or Bridge Executed From Non-Standard Path
id: 2d7b9e41-6c3a-4f82-b1d5-9a0c3e7f5b2d
status: experimental
description: Detects execution of Trezor wallet software (Trezor Suite or trezord bridge) from outside default installation directories. Trojanized wallet companion software is a common companion technique to hardware-wallet targeting and seed-theft campaigns.
references:
  - https://www.bleepingcomputer.com/news/cryptocurrency/trezor-confirms-crypto-stealing-implants-in-three-wallets-releases-fix/
  - https://attack.mitre.org/techniques/T1195/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1195
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\Trezor Suite.exe'
      - '\trezord.exe'
      - '\trezor-bridge.exe'
  filter_legit_paths:
    Image|startswith:
      - 'C:\Program Files\Trezor Suite\'
      - 'C:\Program Files (x86)\Trezor Bridge\'
      - 'C:\Program Files\Trezor Bridge\'
  condition: selection_img and not filter_legit_paths
falsepositives:
  - Portable installations or non-default install directories chosen by users
level: high

KQL (Microsoft Sentinel / Defender)

Use this to enumerate every endpoint where a Trezor device has been connected, so you can scope which users need device-provenance verification and seed rotation guidance. The second query surfaces wallet software executing from unusual locations.

KQL — Microsoft Sentinel / Defender
// Hunt 1: Trezor USB device connections (Defender PnP telemetry) — scope Safe 5 exposure
DeviceEvents
| where Timestamp > ago(90d)
| where ActionType has_any ("PnpDeviceConnected", "UsbDeviceMounted")
| extend ParsedFields = parse_json(AdditionalFields)
| where tostring(ParsedFields.DeviceDescription) has_any ("Trezor", "Safe 5")
   or tostring(ParsedFields.DeviceId) has "VID_1209"
   or tostring(AdditionalFields) has "VID_1209"
| project Timestamp, DeviceName, DeviceId = tostring(ParsedFields.DeviceId),
          DeviceDescription = tostring(ParsedFields.DeviceDescription),
          ReportId, InitiatingProcessAccountName
| summarize FirstSeen = min(Timestamp), LastSeen = max(Timestamp) by DeviceName, DeviceDescription
| order by LastSeen desc

// Hunt 2: Trezor Suite / bridge processes outside standard install paths (possible trojanized wallet software)
DeviceProcessEvents
| where Timestamp > ago(30d)
| where FileName has_any ("Trezor Suite.exe", "trezord.exe", "trezor-bridge.exe")
| where FolderPath !startswith "C:\\Program Files\\Trezor Suite\\"
   and FolderPath !startswith "C:\\Program Files\\Trezor Bridge\\"
   and FolderPath !startswith "C:\\Program Files (x86)\\Trezor Bridge\\"
| project Timestamp, DeviceName, AccountName, FileName, FolderPath, ProcessCommandLine, SHA256
| order by Timestamp desc

Velociraptor VQL

This artifact sweeps the USBSTOR and USB device registry keys for Trezor VID 1209 artifacts — useful for retro-scoping hardware-wallet connections across a fleet during an IR engagement, including devices connected before your EDR retention window.

VQL — Velociraptor
-- Hunt: Enumerate historical Trezor device connections via USB registry artifacts
-- Scopes hardware-wallet exposure for supply-chain IR (Trezor VID_1209 / SatoshiLabs)
SELECT FullPath AS RegistryKey,
       basename(path=FullPath) AS DeviceInstance,
       Data.value AS DeviceData,
       Mtime AS LastWrite
FROM glob(globs='HKLM/SYSTEM/CurrentControlSet/Enum/USB/VID_1209*/**',
          accessor='registry')
UNION ALL
SELECT FullPath AS RegistryKey,
       basename(path=FullPath) AS DeviceInstance,
       Data.value AS DeviceData,
       Mtime AS LastWrite
FROM glob(globs='HKLM/SYSTEM/CurrentControlSet/Enum/USBSTOR/**/*',
          accessor='registry')
WHERE DeviceData =~ 'TREZOR|SatoshiLabs'
ORDER BY LastWrite DESC

Remediation & Verification Script

This PowerShell script inventories currently connected and previously installed Trezor devices on a Windows endpoint, flags anything matching the affected product line, and checks whether Trezor Suite is installed and current enough to run Trezor's device-authenticity verification. Run it across endpoints identified in the hunts above.

PowerShell
# Trezor Safe 5 Supply-Chain Exposure Check — Security Arsenal
# Run elevated. Outputs a JSON report per endpoint for central collection.

$report = [ordered]@{
    Hostname          = $env:COMPUTERNAME
    ScanTime          = (Get-Date).ToString('o')
    ConnectedDevices  = @()
    HistoricalDevices = @()
    TrezorSuite       = $null
    RiskFlags         = @()
}

# 1. Currently connected PnP devices matching Trezor (VID_1209 = SatoshiLabs)
$report.ConnectedDevices = Get-PnpDevice -PresentOnly -ErrorAction SilentlyContinue |
    Where-Object { $_.InstanceId -match 'VID_1209' -or $_.FriendlyName -match 'Trezor' } |
    Select-Object FriendlyName, InstanceId, Status, Class

# 2. Historical USB artifacts (includes disconnected devices) from the registry
$usbEnum = 'HKLM:SYSTEMCurrentControlSetEnumUSB' -replace '\\b','\'
$report.HistoricalDevices = Get-ChildItem "$usbEnum" -ErrorAction SilentlyContinue |
    Where-Object { $_.PSChildName -match 'VID_1209' } |
    ForEach-Object {
        Get-ChildItem $_.PSPath | ForEach-Object {
            [pscustomobject]@{
                DeviceId   = $_.GetValue('DeviceDesc')
                Service    = $_.GetValue('Service')
                InstanceId = $_.PSChildName
            }
        }
    }

# 3. Trezor Suite presence and version
$suite = Get-ItemProperty 'HKLM:SOFTWAREMicrosoftWindowsCurrentVersionUninstall*',
         'HKLM:SOFTWAREWOW6432NodeMicrosoftWindowsCurrentVersionUninstall*' `
         -ErrorAction SilentlyContinue |
         Where-Object { $_.DisplayName -match 'Trezor' } |
         Select-Object DisplayName, DisplayVersion, InstallLocation, Publisher
$report.TrezorSuite = $suite

# 4. Risk flagging
if ($report.ConnectedDevices -or $report.HistoricalDevices) {
    $report.RiskFlags += 'TREZOR_DEVICE_PRESENT: Verify purchase provenance (official Trezor shop vs. reseller); run device-authenticity check in Trezor Suite.'
}
if ($suite -and $suite.Publisher -notmatch 'SatoshiLabs') {
    $report.RiskFlags += 'UNEXPECTED_PUBLISHER: Trezor software publisher mismatch — possible trojanized installer.'
}
if ($suite -and [version]($suite.DisplayVersion -replace '[^0-9.]','') -lt [version]'25.1.1') {
    $report.RiskFlags += 'OUTDATED_SUITE: Update Trezor Suite to the latest release to obtain the implant-detection/device-authenticity fix.'
}

$report | ConvertTo-Json -Depth 5

Remediation

If you or your organization owns a Safe 5 purchased through CryptoBilis or any unofficial reseller:

  1. Stop using the device immediately. Do not enter a recovery phrase into it, do not generate new seeds on it, and do not assume stored funds are safe.
  2. Migrate funds now. Using a known-clean, newly initialized device purchased directly from Trezor (or a verified alternative), generate a new recovery phrase and move all assets off the suspect seed. Treat the old seed as fully compromised — because with a captured phrase, it is.
  3. Update Trezor Suite and device firmware. Trezor has released a fix that includes device-authenticity verification to identify tampered units. Update through the official Trezor Suite only, downloaded from trezor.io — never via links in email, ads, or third-party download sites. Verify the Suite installer publisher is SatoshiLabs before running it.
  4. Run Trezor's device-authenticity check. The updated Suite/firmware verification flow is designed to flag devices whose hardware or firmware does not match genuine manufacturing records. A failed check on a reseller-sourced device is grounds for immediate seed rotation.
  5. Verify provenance across your fleet. Use the hunts and script above to find every endpoint that has touched a Trezor device, interview the owners on purchase source, and quarantine any unit not purchased directly from Trezor's official shop or an explicitly authorized distributor.
  6. Reset and re-initialize suspect devices only after funds are migrated — and even then, treat a physically implanted device as untrusted hardware. Factory resets do not remove a hardware implant.

Organizational hardening going forward:

  • Procurement policy: Hardware wallets and other security-critical devices (U2F/FIDO2 keys, HSMs) must be purchased directly from the manufacturer or documented authorized distributors. Add this to your procurement standard today; "cheaper on a marketplace" is how implants arrive.
  • Adopt passphrases (BIP-39 passphrase / "hidden wallets"): A strong passphrase means a stolen seed phrase alone does not yield usable keys. It does not make a compromised device safe, but it materially raises the bar against exactly this attack class.
  • Consider multi-signature or distributed custody for organizational funds: No single device — compromised or not — should be a single point of failure for treasury assets.
  • Physical inspection on receipt: Check packaging seals, holographic stickers, and device weight/finish against manufacturer documentation. Report anomalies to the vendor before initializing the device.
  • Threat-model note for your IR playbooks: Add "hardware supply-chain compromise" as a scenario. Your existing playbooks assume software intrusions; a seeded-device compromise requires seed rotation and fund migration steps that most IR plans do not contain.

The Bottom Line

Three confirmed devices is a small number — but supply-chain implants are never about the confirmed count. They are about the unknown population in the channel and the irreversibility of the theft once a seed is captured. The cellular exfiltration path makes this attack invisible to every network control you own. The only durable defenses are provenance verification, device-authenticity checks, passphrase hardening, and immediate fund migration when trust in a device is lost. If any Safe 5 in your environment came from CryptoBilis or another unofficial Southeast Asian reseller, start the migration today — the attacker already has everything they need.

Related Resources

Security Arsenal Alert Triage Automation AlertMonitor Platform Book a SOC Assessment platform Intel Hub

alert-triagealert-fatiguesoc-automationfalse-positive-reductionalertmonitortrezorsupply-chain-attackhardware-implantcryptocurrency-thefthardware-wallet

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.

Book a SOC AssessmentSee AlertMonitor in Action