A newly whitelisted contract drained over $6 million in wstETH from a Base vault with seven unnamed signers

Blockaid's tally stood at about $2.02 million at 09:21 UTC and passed $6 million roughly 40 minutes later ^[2]. Close to $4 million moved in those 40 minutes, about $100,000 a minute ^[18]. Exvul counted six outflows ^[5], so the average transfer was about 297 wstETH ^[14], or roughly $1 million ^[16]. The reported totals put wstETH at no less than about $3,365 a token ^[15].

Aave handled the exit. The draining contract borrowed 1,783.067 aBaswstETH, Aave's receipt token for wrapped staked ether deposited on Base, and redeemed it through Aave into about 1,783 wstETH ^[3]. Security firms have not said any core contracts were compromised, and Base itself was not hacked ^[6]. The step that went wrong came before Aave was involved: a newly created contract was added to the vault's own whitelist ^[4].

Who could edit that whitelist is where the public record stops. The vault is an OpenZeppelin transparent proxy owned by a Safe created about 324 days ago that needs three of seven signatures to act ^[8]. None of the seven signers has been identified, and no protocol has claimed the vault ^[7]. If the change went through that Safe, any of 35 different trios could have signed it ^[17]. Upgrade authority sits with a separate contract, a further layer between the vault and whoever ultimately controls it ^[13].

According to Bitcoin.com, investigators cannot yet tell whether the whitelist change came from stolen credentials, a white hacker, faulty permissions or another weakness ^[10]. Each answer puts the loss in a different place. Stolen signer keys make it a failure of key custody by people nobody can name. A white hacker leaves room for the 1,783 tokens to come back. A permission error in the vault's configuration is a bug in one operator's setup.

I think the evidence supports locating the risk in this vault's custody arrangement, or more precisely in the whitelist permission that arrangement was supposed to guard. The counter-case is specific. The Safe was deployed through Safe Proxy Factory 1.4.1, according to Basescan and Arkham Intelligence ^[9], and the vault sits on a standard OpenZeppelin proxy ^[8]. If a post-mortem traced the whitelist change to a flaw in either shared component, the exposure would reach every contract built the same way, and this view would be wrong. No one has published a confirmed account of a bug or a key compromise ^[12].

For anyone allocating money, the open question is whose wstETH this was. With no owner come forward, it is not known whether the tokens belonged to the signers themselves or to depositors who trusted them ^[7]. The wider market cost may come from the sale. Bitcoin.com reported that the risk to the broader system looks limited for now, but that selling the stolen wstETH could weigh on its peg in the short term ^[11].