NEAR Intents exploit
How this score was reached
100critical risk
LowMediumHigh
direct95
- deposited to sanctioned entity (90)
- this address is itself flagged: hack — NEAR Intents exploit (90)
- Named as a perpetrator in NEAR Intents exploit, occurred 30 Sep 2026, media
inbound63
Where the risk came from
•Contact with 4 designated addresses, largest $0.00. Scored 0: value below the materiality threshold, but contact with a designated address is reportable on its own.•1 payment to designated address, strongest 90 — 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).
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.
sanctionshack2 unpriced
Risk sources
1 in · 1 out| Role | Class | Source | Hop | Value ≤ | Score | |
|---|---|---|---|---|---|---|
| drives score | hack | NEAR Intents exploit via 0x168f36…0cf3b7 | 1 | — | 63 | |
| paid out | sanctions | 0x098b71…3e2f96 OFAC SDN list | 1 | — | 90 |
Risk
- Dominant source
- NEAR Intents exploithop 0 · score 90.0
Who it is
- Activity
- Hack
Incidents
1NEAR Intents exploit
Role: Perpetrator· hack· 2026-09-30
confirmedDirect
