NEAR Intents exploit
How this score was reached
100critical risk
LowMediumHigh
direct95
- this address is itself flagged: hack — NEAR Intents exploit (90)
- Named as a perpetrator in NEAR Intents exploit, occurred 30 Sep 2026, media
inbound63
outbound0
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.•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.
hackline = score in force (63)faint = not counted4 unpriced
Risk sources
2 in| Role | Class | Source | Hop | Value ≤ | Score | |
|---|---|---|---|---|---|---|
| drives score | hack | NEAR Intents exploit via 0x09fd1f…b3ad37 | 1 | — | 63 | |
| context | hack | 3 sources via 0xcd87ff…7eb262 | 2 | — | 44.10 |
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
