NEAR Intents reports $3.8 million loss after smart contract bug
- Published
- Updated
- Since then
- 35 new reports
NEAR Intents reported a security incident tied to its Omni deposit and withdrawal setup and its smart contract, with a preliminary loss of about $3.8 million. The protocol paused services, later said the flaw was patched and compensation would be full, and then said the full amount had been returned and its investigation was closed.
Key claims & sources
What it means
Users on the affected networks are the people who would notice this first the next morning: deposits and withdrawals were paused, and later most services were restored while some disruption continued. The event also reached the broader NEAR market, which was still reacting around the time the incident was disclosed.
In practice, NEAR Intents shifted from a halted state to partial restoration, while keeping its promise to cover losses in full. What did not change is that the protocol still treated the incident as a security issue tied to its own infrastructure and contract interaction.
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 3.6 years ago | Patricio Worthalter · Phishing attack incident | $3.8M |
| 2.1 years ago | Onyx · Contract vulnerability incident | $3.8M |
| 3.6 years ago | Rocket Pool · Phishing incident | $3.8M |
| 4.4 years ago | XCarnival · Deposit Logic Flaw incident | $3.8M |
| 5.7 years ago | DODO AMM · Improper Access Control incident | $3.8M |
4282 incidents stored · 569 were as large as this one or larger ($3.8M)