A double-counted share reduction let an attacker pull $86,000 from UNCX's shared vesting pool
An attacker took about $86,000 from UNCX's shared Ethereum vesting pool on Oct. 14, according to security firm Blockaid. About $3.25 million was still in the contract when Blockaid flagged the attack as ongoing.
The Investor · Invest desk
UNCX's later update puts the count of affected tokens at 10. The initial theft report named 5: EDGEN, ZC, PEPECOIN, LO0P and PAAL. Blockaid identified an $86,000 exploit against the pool.
| Figure | Value | Note | Claim |
|---|---|---|---|
| Affected tokens, per later UNCX update | 10 tokens | 8 | |
| Initially reported tokens | 5 tokens | 7 | |
| Exploit, per Blockaid | 86,000 US dollars | 1 |
What happened
- Exvul researchers traced the flaw to UNCX's VestingManager contract and how it handles released and canceled token shares, which are accounting claims against tokens held in the contract.
- The first count of affected tokens was five: EDGEN, ZC, PEPECOIN, LO0P and PAAL.
- A later update from UNCX raised the number of affected tokens to ten.
- UNCX restricted new vesting positions while questions persisted over the balance left in the pool.
Why it matters
- exposure Every project with tokens in the shared pool held a claim against the same ledger, so a bad entry reached deposits that belonged to other users.
- contradiction The headline loss came with a five-token count while UNCX's own update says ten, so $86,000 cannot yet be read as the full loss.
- constraint With new vesting positions restricted, projects that wanted to lock tokens through the pool cannot do so until UNCX lifts the limit.
- decision The saving from sharing a contract now has a loss beside it: $86,000 taken, with about $3.25 million exposed at the time of the alert.
The fault is a ledger entry updated in one place and not in another. Exvul's researchers found that the contract's release() function reduced the global _totalTokenShares figure without removing the released shares from the position's _depositedShares record [3]. When the position was cancelled later, the contract deducted shares using the original recorded deposit, so the same reduction was counted twice, and a direct token donation distorted the totals further [4]. Blockaid, the firm that raised the alarm, described the sequence on X. "The attacker created vesting positions in the shared token pool, released a large one, donated tokens in, then cancelled a topped-up vest so a tiny leftover vest could withdraw other users' locked tokens," Blockaid wrote [5].
The loss is small against the balance it was drawn from. Set $86,000 [1] against the roughly $3.25 million still in the contract when Blockaid identified the attack as ongoing [6] and the loss is about 2.6% [12]. That ratio is only as good as its inputs. The report pairs the $86,000 with the first five-token count, dates the $3.25 million to the moment of the alert, and does not say what the pool holds now or whether the loss was restated after UNCX's update.
We think the failure sits in the bookkeeping, and a shared pool is the costlier place for it. The case for a shared pool is that it is convenient, generally less expensive and easier to manage; the price is that when the shared bookkeeping goes wrong, funds belonging to unrelated projects land in the same predicament [11]. The counter-thesis is that this was one pair of functions in one contract with about 2.6% of the balance gone [12], and that a separate contract per allocation would carry code risk of its own. Both readings fit what has been published. We would drop the liability reading if the remaining balance reconciles with recorded deposits after a fix and the loss stops at the attacker's proceeds.
UNCX has restricted new vesting positions [9]. That is new lock business it has stopped taking in the pool, from a platform whose product is evidence that assets cannot be sold before an agreed date [10]. The platform, formerly known as Unicrypt, has operated since 2020 [10].
What to watch
- A token-by-token tally from UNCX across all ten tokens, and whether the $86,000 figure is restated.
- Whether UNCX reconciles the pool's remaining balance against recorded deposits before it lifts the limit on new vesting positions.
- A post-mortem from UNCX or Exvul confirming how release() and cancellation now track shares.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence58
- Adoption
- Insufficient
- Hype gap−5
- Incentives
- Insufficient
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Security firm Blockaid identified an $86,000 exploit against UNCX's shared Ethereum vesting pool on Oct. 14.
- [2]
Exvul security researchers traced the vulnerability to UNCX's VestingManager contract and its handling of released and canceled token shares, which represent accounting claims against tokens held inside the contract.
- [3]
According to Exvul, the contract's release() function reduced the global _totalTokenShares figure without correspondingly removing released shares from the position's _depositedShares record.
- [4]
When the position was later canceled, the contract deducted shares using the original recorded deposit, effectively counting the same reduction twice, and a direct token donation further distorted the arithmetic.
- [5]
Blockaid wrote on X: "The attacker created vesting positions in the shared token pool, released a large one, donated tokens in, then cancelled a topped-up vest so a tiny leftover vest could withdraw other users' locked tokens."
- [6]
Approximately $3.25 million was still sitting inside the affected Ethereum smart contract when Blockaid identified the attack as ongoing.
- [7]
The initially reported theft involved five cryptocurrencies: EDGEN, ZC, PEPECOIN, LO0P and PAAL.
- [8]
A later update from UNCX shifted the count of affected tokens to ten.
- [9]
UNCX restricted new vesting positions as questions persisted over the $3.25 million remaining in the pool.
- [10]
UNCX Network, formerly known as Unicrypt, has operated since 2020 and gives crypto projects tools to lock liquidity and distribute tokens on set schedules, which helps founders, developers and investors show that certain assets cannot be sold before an agreed date.
- [11]
In a shared vesting pool, multiple DeFi projects place tokens in common smart-contract infrastructure; the arrangement is convenient, generally less expensive and easier to manage, but when the shared bookkeeping goes wrong, funds belonging to unrelated projects can be affected together.
- [12]
The $86,000 loss is about 2.6% of the roughly $3.25 million remaining in the contract when the attack was identified as ongoing.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
2 independent publishers whose own reporting we read for this story.
- cryptobriefing.comUNCX Network vesting pool exploited for $86,000, Blockaid reports
1 article · October 14, 2026
- news.bitcoin.comAn $86,000 Exploit Rocks a Crypto Pool Built to Lock Tokens
1 article · October 14, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Smart contract exploitsFollow
- Token vesting and unlocksFollow
- DeFi SecurityFollow