$NEAR $3.8M disappeared from NEAR Intents — and the interesting part is where the failure happened.
NEAR Intents said today that a bug involving its Omni deposit-and-withdrawal infrastructure and smart contracts led to roughly $3.8 million in losses. The team says the vulnerability has been patched and affected users will be fully compensated. Deposits and withdrawals across several networks were also paused while the fix is completed.
What catches my attention is that this doesn’t look like a simple “the blockchain was hacked” story. The reported weakness sits around the infrastructure connecting assets across chains.
That distinction matters.
Cross-chain systems are basically trust pipelines. Every extra bridge, custody layer, settlement mechanism or contract interaction creates another place where assumptions have to hold. You can have good monitoring on one side and still get hurt when two components interact in a way nobody expected.
And honestly, that’s probably the bigger lesson here.
NEAR Intents had just demonstrated its ability to block much of a separate large illicit flow days earlier. Now its own infrastructure has taken a hit.
The team says users will be made whole, but the compensation is still a promise rather than a completed reimbursement.
So I’m watching the recovery process as closely as the exploit itself.
Still trying to figure out what this actually changes.
NEAR Intents said today that a bug involving its Omni deposit-and-withdrawal infrastructure and smart contracts led to roughly $3.8 million in losses. The team says the vulnerability has been patched and affected users will be fully compensated. Deposits and withdrawals across several networks were also paused while the fix is completed.
What catches my attention is that this doesn’t look like a simple “the blockchain was hacked” story. The reported weakness sits around the infrastructure connecting assets across chains.
That distinction matters.
Cross-chain systems are basically trust pipelines. Every extra bridge, custody layer, settlement mechanism or contract interaction creates another place where assumptions have to hold. You can have good monitoring on one side and still get hurt when two components interact in a way nobody expected.
And honestly, that’s probably the bigger lesson here.
NEAR Intents had just demonstrated its ability to block much of a separate large illicit flow days earlier. Now its own infrastructure has taken a hit.
The team says users will be made whole, but the compensation is still a promise rather than a completed reimbursement.
So I’m watching the recovery process as closely as the exploit itself.
Still trying to figure out what this actually changes.