Coldcard
How this score was reached
100critical risk
LowMediumHigh
direct95
- deposited to mixer (80)
- this address is itself flagged: hack — Coldcard (90)
- Mentioned in Chainabuse report: Hack, community report, alleged, not confirmed, occurred 3 Sep 2026, social
- Named as a perpetrator in Coldcard, occurred 30 Jul 2026, media
inbound80
Where the risk came from
•2 payments to designated addresses, strongest 80 — shown to the RIGHT of this address. Paying a designated party is the offence itself, so it counts as direct exposure.•aml 100.0 = 80, the single strongest source (mixer, 1 hop away).
Edge thickness is risk score (0–100), not an amount. The dollar figure on a node is the ceiling on what could have travelled that path — its narrowest hop, priced on the day it happened — not the sum received; “—” means unpriced, which is not $0. Dashed = intermediate hops; click a path or a node to walk it step by step. Hover the graph or the table.
mixerin ≤ $2,4392 unpriced
Risk sources
1 in · 1 out| Role | Class | Source | Hop | Value ≤ | Score | |
|---|---|---|---|---|---|---|
| drives score | mixer | Tornado.Cash via 0x47ce0c…3c2936 | 1 | ≤ $2,439 | 80 | |
| paid out | mixer | 2 addresses privacy tooling (entity attribution) | 1 | — | 80 |
Risk
- Dominant source
- Coldcardhop 0 · score 90.0
Who it is
- Activity
- Hack
Incidents
2Mentioned in Chainabuse report: Hack
Role: Perpetrator· hack· 2026-09-03
Community reportNot confirmed
Coldcard
Role: Perpetrator· hack· 2026-07-30
confirmedDirect
