0x75e85b9475e8…75e85b91

ConfirmedSecurity619 vB148 sat/vB3 min decode

SlowMist: Chain Games Staking Exploit Drained About $20,000

SlowMist says a missing reward checkpoint in Chain Games' staking contract let an attacker replay restake() 360 times, turning 1,000 CHAIN into 36 million shares for about $20,000.

SlowMist Reports Chain Games Staking Exploit Caused About $20,000 in Losses
WitnessSlowMist Reports Chain Games Staking Exploit Caused About $20,000 in LossesPexels / pixabay

Outputs

  1. SlowMist disclosed on Nov. 16 that a Chain Games staking exploit caused about $20,000 in losses.

  2. The contract did not update its reward checkpoint when staking shares moved between contracts.

  3. The attacker called restake() through newly created receiving contracts 360 times.

  4. An initial 1,000 CHAIN stake expanded into more than 36 million shares.

  5. The attacker withdrew the proceeds via the contract's normal withdrawal process.

Blockchain security firm SlowMist disclosed on Nov. 16 that an exploit of Chain Games' staking contract caused roughly $20,000 in losses. The attacker abused a missing reward checkpoint update to claim historical staking rewards 360 times before withdrawing through the contract's normal exit process.

The core defect sits in how the protocol handles staking shares that move between contracts. According to SlowMist, the contract failed to update its reward checkpoint when shares transferred to a new receiving contract. That gap allowed a freshly deployed receiving contract to call restake() and claim historical rewards again — rewards that had already accrued to the shares before the transfer.

The attacker repeated the loop 360 times. An initial stake valued at 1,000 CHAIN, the Chain Games token, grew into more than 36 million shares, SlowMist said. The attacker then withdrew the accumulated value using the contract's standard withdrawal path rather than any additional exploit, leaving the manipulation itself confined to the restaking loop.

How did the reward checkpoint gap work?

Staking systems typically record a checkpoint — a snapshot of each account's reward entitlement — whenever shares move. The checkpoint prevents the same reward span from being claimed twice by different contracts holding the same underlying shares. Chain Games' implementation skipped that update step on inter-contract share transfers, SlowMist found.

The result: each newly created receiving contract inherited the historical reward state of the shares it received. By calling restake(), the new contract could re-claim rewards that the original position had already earned and collected. Deploying a fresh receiving contract and repeating the call reset the cycle, which is what produced the 360 recorded iterations.

The arithmetic of the attack follows directly from the loop. One thousand CHAIN became more than 36 million shares — a multiple that reflects compounded re-claims rather than organic staking growth. Each iteration added historical rewards back into the position, compounding the share count until the attacker cashed out.

What are the operational consequences?

The damage, at approximately $20,000, is modest by the standards of 2024-era protocol exploits, which routinely run into eight figures. The significance is structural. The bug class — a stale checkpoint on share migration — is a known pattern in staking and vault designs, and it is detectable in review before deployment. Any protocol that moves shares between contracts without resetting reward accounting carries the same exposure, regardless of the value currently at stake.

For Chain Games, the incident implies remediation work on the staking contract's accounting: checkpoint updates must fire on every share transfer, and reward claims must be idempotent — payable once per reward span, not once per calling contract. Until that fix ships and is audited, staking positions in the affected contract remain exposed to the same replay technique.

The relatively low loss figure also reflects a constraint on the attacker rather than a limit on the bug. The exploit's ceiling depends on the rewards available in the pool, the size of the initial stake and gas costs across 360 transactions. A larger reward pool or a bigger seed position would scale the loss proportionally under the identical defect.

What comes next?

SlowMist's Nov. 16 disclosure gives the Chain Games team a documented technical account of the flaw: the missing checkpoint update, the restake() replay path and the 360-iteration extraction into more than 36 million shares. The standard sequence from here is a contract patch or migration, an independent audit of the revised reward accounting, and a public post-mortem from the project. Users of the staking contract should watch for the project's confirmation that checkpoint logic now updates on all share movements before treating the pool as safe for new deposits.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles