summer-fi-exploit-2026-07
How this score was reached
100critical risk
LowMediumHigh
direct95
- this address is itself flagged: hack — summer-fi-exploit-2026-07 (90)
- Named as a perpetrator in Lazy Summer Protocol, occurred 6 Jul 2026, media
- Named as a perpetrator in summer-fi-exploit-2026-07, occurred 6 Jul 2026, media
- Named as a perpetrator in Summer Finance, occurred 9 Jul 2026, media
inbound40
outbound0
Where the risk came from
•aml 100.0 = 40, the single strongest source (sanctions, 5 hops away). The other 8 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.
sanctionshackmixerphishingline = score in force (40)faint = not countedin ≤ $1.5M
Risk sources
5 in| Role | Class | Source | Hop | Value ≤ | Score | |
|---|---|---|---|---|---|---|
| drives score | sanctions | 3 sources via 0xe9cda4…70cb06 | 5 | ≤ $87,800 | 40 | |
| context | mixer | Railgun via 0xe9cda4…70cb06 | 4 | ≤ $774,392 | 30 | |
| context | mixer | 2 sources via 0xe9cda4…70cb06 | 5 | ≤ $1,019 | 20 | |
| context | hack | Indexed finance exploit (Etherscan public label) via 0xe9cda4…70cb06 | 5 | ≤ $175.43 | 15.13 | |
| context | phishing | 2 sources via 0xe9cda4…70cb06 | 4 | ≤ $1.5M | 8 |
Risk
- Dominant source
- summer-fi-exploit-2026-07hop 0 · score 90.0
Who it is
- Activity
- Hack
Incidents
3Lazy Summer Protocol
Role: Perpetrator· hack· 2026-07-06
confirmedDirect
summer-fi-exploit-2026-07
Role: Perpetrator· hack· 2026-07-06
confirmedDirect
Summer Finance
Role: Perpetrator· hack· 2026-07-09
confirmedDirect
