kelp-dao-rseth-bridge-2026-04
How this score was reached
100critical risk
LowMediumHigh
direct95
- deposited to mixer (80)
- this address is itself flagged: hack — kelp-dao-rseth-bridge-2026-04 (90)
- Named as a perpetrator in kelp-dao-rseth-bridge-2026-04, occurred 18 Apr 2026, media
inbound63
Where the risk came from
•1 payment to designated address, 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 = 63, the single strongest source (hack, 1 hop away). The other 3 sources shown below are real exposure, but add nothing to the score: the rule is a maximum, not a sum.
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.
hackmixerline = score in force (63)faint = not countedin ≤ $83,5701 unpriced
Risk sources
2 in · 1 out| Role | Class | Source | Hop | Value ≤ | Score | |
|---|---|---|---|---|---|---|
| drives score | hack | kelp-dao-rseth-bridge-2026-04 via 0x496b28…1dfabe | 1 | ≤ $83,570 | 63 | |
| context | hack | 3 sources via kelp-dao-rseth-bridge-2026-04 | 4 | ≤ $83,570 | 21.61 | |
| paid out | mixer | 0xfb2dc5…685401 privacy tooling (entity attribution) | 1 | — | 80 |
Risk
- Dominant source
- kelp-dao-rseth-bridge-2026-04hop 0 · score 90.0
Who it is
- Activity
- Hack
Incidents
1kelp-dao-rseth-bridge-2026-04
Role: Perpetrator· hack· 2026-04-18
confirmedDirect
