C.R.E.A.M. Finance Pauses AMP Market After Reentrancy Exploit

C.R.E.A.M. Finance’s Ethereum lending market was exploited on August 30, 2021, after an attacker used AMP token-transfer callbacks to re-enter the protocol’s borrowing process before C.R.E.A.M. had finished updating its internal accounting. The incident forced the protocol to pause AMP supply and borrowing and highlighted a central risk of decentralized finance: individually functioning components can become unsafe when their execution order is combined incorrectly.

Contemporaneous reporting said C.R.E.A.M. initially identified losses of 418,311,571 AMP and 1,308.09 ETH. The Block characterized the incident as an approximately $18.8 million exploit in coverage published at 5:59 p.m. EDT and updated at 6:18 p.m. EDT on August 30. That dollar figure should be treated as an event-day estimate, not a reproducible closing valuation: the report did not identify a pricing venue, index or exact asset-price timestamp.

Independent security analysis subsequently traced the affected activity to 05:44:47 UTC on August 30. The transaction record and later protocol analysis established that the incident occurred on the assigned date, despite an apparent date inconsistency in C.R.E.A.M.’s September 1 post-mortem, which described the approximate time as noon on August 31 in UTC+8.

How the borrowing sequence broke

AMP uses transfer-hook behavior resembling the ERC-777 standard. That design permits a receiving contract to execute a callback when tokens arrive. A callback is not inherently a vulnerability, but it requires interacting applications to assume that external code may run during a transfer.

C.R.E.A.M.’s borrowing sequence transferred AMP before recording the completed loan in storage. The attacker arranged for AMP’s recipient hook to call back into C.R.E.A.M. and initiate another borrow while the first loan still appeared unfinished. In effect, the same collateral state could support an additional loan before the protocol’s books reflected the original one.

Early descriptions on August 30 attributed the problem to a reentrancy issue associated with AMP. That framing was incomplete. C.R.E.A.M.’s primary post-mortem, published on September 1, said AMP operated as designed and identified C.R.E.A.M.’s integration as the root cause. The protocol said the technique was repeated across 17 transactions and that a smaller copycat attack also occurred.

Why it mattered

The exploit was significant beyond its immediate losses because C.R.E.A.M. was a permissionless lending system built around composability: tokens, lending contracts, liquidations and short-duration liquidity could be assembled inside one transaction. That flexibility also expanded the attack surface. A token feature considered valid in isolation became dangerous when the lending contract made an external transfer before committing its accounting state.

The incident therefore illustrated the difference between auditing a component and evaluating an integration. Supporting a new asset required C.R.E.A.M. to examine not only its balance and collateral parameters but also nonstandard transfer behavior, callbacks and cross-market reentrancy. On September 1, the protocol said it would strengthen listing reviews, scan for external calls and add a protocol-level reentrancy guard.

C.R.E.A.M. reported on August 30 that AMP supply and borrowing had been paused and that other markets were not affected. Those were contemporaneous protocol claims; the surviving event-day record did not provide a complete independent accounting of every user position or bad debt.

Later clarification

C.R.E.A.M.’s September 1 post-mortem increased the reported total to 462,079,976 AMP and 2,804.96 ETH across the main and copycat activity. Those figures clarify the later investigation and should not be substituted for what market participants were initially told on August 30. The later report also committed protocol fees toward replacing affected assets, but that promise was not an event-day recovery result.