NEAR Intents Publishes Security Incident Postmortem Report, 3800000 USD All Funds Recovered
BIBIBI
AT A GLANCE
NEAR Intents disclosed a contract vulnerability; approximately 3800000 USD in fraudulent balances were withdrawn and have since been fully recovered.
Article
NEAR Intents Publishes Security Incident Postmortem Report, 3800000 USD All Funds Recovered
PANews October 17 reported that NEAR Intents published October 1 a security incident report stating that its smart contract had a vulnerability related to interactions with a third-party contract. Attackers exploited the refund mechanism following failed calls, causing funds to be returned while the deposits were still recorded. Through 23 failed deposit transactions, approximately 3800000 USD in fraudulent balances were generated, and the funds were subsequently withdrawn through the Omni cross-chain infrastructure. This was a vulnerability in the NEAR Intents contract itself, not a vulnerability in the Omni infrastructure. Within 36 hours of discovering the vulnerability, all funds had been fully recovered. The team removed the relevant deposit notification function, introduced abnormal-balance monitoring and an automatic pause mechanism, and paid October 7 a bounty to the researcher who reported another critical vulnerability in the same function. The system has now returned to normal.
NEAR Intents published a October 1 security incident report.
02
The vulnerability was related to interactions between the smart contract and a third-party contract.
03
Attackers exploited the refund mechanism following failed calls, generating approximately 23 failed deposit transactions and approximately 3800000 USD in fraudulent balances.
04
The funds were subsequently withdrawn through the Omni cross-chain infrastructure.
05
The report stated that this was a vulnerability in the NEAR Intents contract, not a vulnerability in the Omni infrastructure.
06
Within 36 hours of discovering the vulnerability, all funds had been fully recovered.
07
The team removed the relevant deposit notification function and introduced abnormal-balance monitoring and an automatic pause mechanism.
08
The team paid October 7 a bounty to the researcher who reported another critical vulnerability in the same function. 300000 USD The report stated that the system has now returned to normal.
09
The report stated that the system has now returned to normal.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
In simple terms, the contract recorded funds that had not actually been deposited, causing account balances to be artificially inflated and withdrawn. The team stated that the funds had been recovered and added monitoring and automatic pause measures.
Why it matters to readers
This indicates that when smart contracts interact with external contracts, refund and balance-recording logic may create fund risks. The remediation measures may reduce the likelihood of recurrence, but their long-term effectiveness remains to be observed.
Users should understand the following: a displayed balance does not necessarily equal actual funds, and contract vulnerabilities may affect asset security.
Risks and unknowns
The evidence did not provide independent audit or third-party verification results.
The evidence did not state how long the remediation measures had been validated through stable operation.
The evidence does not provide complete technical remediation details.
The evidence does not specify 300000 USD the specific recipient of the bounty.
Related Developments
Loading event timeline…
Related concepts
Smart Contracts
This term is not in the glossary yet. Browse related concepts in the glossary.
