UNCX Vesting V2 Exploit Spreads Across Four Chains, Losses Near $1.5M

UNCX Network said its Vesting V2 contracts were exploited across Ethereum, BNB Chain, Base and Robinhood Chain, affecting ten tokens. Independent onchain analysis estimated total losses at about $1.49 million after copycat wallets and automated trading bots expanded the incident. The estimate is preliminary and may change as affected assets and transactions are reviewed. Follow verified incident updates in OrangeX.com Crypto News.

What the operator confirmed

In its October 14 statement, UNCX said the incident was limited to Vesting V2. The operator said its liquidity-locking products and legacy vesting contracts were not affected. It also described temporary containment measures, including fee and function changes intended to make further exploitation uneconomic while the team investigated.

UNCX said it was coordinating with law enforcement and an industry incident-response group on recovery planning. At drafting time, no recovered amount or final reimbursement plan had been confirmed. Users should rely on the operator's official channels for contract-specific instructions and avoid unsolicited recovery links. Broader threat coverage is available in OrangeX.com Security News.

Preliminary loss estimate and attack path

Onchain researchers estimated roughly $969,000 in losses on BNB Chain, $242,000 on Ethereum, $169,000 on Robinhood Chain and $114,000 on Base. These figures total about $1.49 million and include activity attributed to copycats and MEV bots, so they should not be treated as a final audited loss statement.

The preliminary technical assessment points to a share-accounting flaw in the Vesting V2 flow. Researchers said an attacker could manipulate the sequence of opening, topping up, releasing and canceling vesting positions so the contract counted value incorrectly. That root-cause description remains subject to confirmation by a full post-mortem and contract-level review.

What users and token teams should check

The incident does not mean every UNCX product or every token using UNCX was compromised. Token teams should first identify the exact chain, contract version and pool involved, then compare those details with the operator's affected-token list. Users should not approve transactions or connect wallets to sites claiming to provide emergency recovery unless the destination is verified independently.

For protocols, the event highlights the need to test accounting invariants across complex state transitions, not only single-function calls. Cross-chain deployments also require coordinated pause controls, monitoring and communication because a reusable flaw can be copied quickly on another network.

OrangeX.com Analysis

The confirmed scope is Vesting V2 across four chains, with ten tokens named by the operator; liquidity lockers and legacy vesting were described as unaffected. The approximate $1.49 million figure is an external onchain estimate, not a final operator audit. The central lesson is that shared accounting logic can turn a local bug into a multi-chain incident once attackers and bots reproduce the transaction pattern. The decisive next facts will be a verified root cause, final loss reconciliation, recovery progress and any contract migration or compensation plan. Track confirmed follow-ups in OrangeX.com Latest News.