Experts blame a 'vanity address' bug for Wintermute's $160 million hack

Quick Take

  • Market making firm Wintermute suffered a $160 million theft on its Ethereum vault, it announced today.
  • Security analysts say the hacker likely took advantage of a recently discovered ‘vanity address’ vulnerability.
 
 

On Tuesday, crypto market making firm Wintermute said that it had $160 million stolen from its Ethereum vault, a type of crypto wallet account holding its assets in a smart contract. 

While the Wintermute team has yet to provide an official post-mortem, security analysts have offered some insights into the hack. According to Mudit Gupta, Polygon's chief information security officer, a vulnerability may well have enabled the hacker to calculate the private keys of the vault’s admin address — allowing them to drain the vault of its funds.

As a market maker, Wintermute maintained several crypto assets in a vault. This vault relied on an admin address with a prefix “0x0000000,” which analysts say is a “vanity address.” At the same time, the vanity address functioned as an admin account (in the form of a hot wallet) to authenticate transactions for Wintermute’s vault.

Vanity addresses contain identifiable names or numbers within them — or have a particular style — and can be generated using certain online tools like Profanity. Last week, decentralized exchange aggregator 1inch published a security disclosure report claiming that “vanity addresses” generated with Profanity were not secure. Per 1inch, the private keys linked to Profanity-generated addresses could be extracted with brute force calculations.

Gupta and other security analysts have hypothesized that since the admin address is a vanity address, the hacker calculated its private key, took over Wintermute’s vault and transferred funds out to another address in their control.

“The vault only allows admins to do these transfers and Wintermute’s hot wallet is an admin, as expected. Therefore, the contracts worked as expected but the admin address itself was likely compromised,” Gupta wrote in a separate blog post.

Gupta said that it seems like Wintermute moved all the ether (ETH) from the vanity address wallet itself prior to the hack, perhaps as a precaution in light of the Profanity disclosures — but the firm didn't change its admin privileges.

THE SCOOP

Keep up with the latest news, trends, charts and views on crypto and DeFi with a new biweekly newsletter from The Block's Frank Chaparro

By signing-up you agree to our Terms of Service and Privacy Policy
By signing-up you agree to our Terms of Service and Privacy Policy

SlowMist, a smart contract security firm, corroborated Gupta’s findings. It told The Block: “After analysis, we think that the reason may be that Wintermute's stolen externally-owned account (EOA) is a wallet created by Profanity (starting with 0x0000000).”

According to SlowMist, the hacker has now deposited $114 million worth of stolen assets into decentralized exchange Curve.

Wintermute hints at the issue

Wintermute founder Evgeny Gaevoy did not reply to a request for comment on whether the vanity address was the cause of the hack. On Twitter, Gaevoy did not address this directly but he quote tweeted a tweet by Yearn Finance lead developer Banteg referencing a previous case of a hack involving vanity addresses, saying, "Karma is a bitch:)"

Why use a vanity address at all? Gupta told The Block that Wintermute may have used one it's considered more gas-efficient for making transactions. Gaevoy confirmed on Twitter that this was why the firm used one.

In the past, contract addresses were created using vanity address generators to have many zeros in them as teams believe such addresses lead to gas savings. Here the cost savings really depend on the usage. For a market maker like WinterMute that does thousands of transactions every day for market making, every bit of gas matters.


© 2023 The Block. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

About Author

Vishal Chawla is The Block’s crypto ecosystems editor and has spent over six years covering tech protocols, cybersecurity, artificial intelligence and cloud computing. Vishal likes to delve deep into blockchain intricacies to ensure readers are well-informed about the continuously evolving crypto landscape. He is also a staunch advocate for rigorous security practices in the space. Before joining The Block, Vishal held positions at IDG ComputerWorld, CIO, and Crypto Briefing. He can be reached on Twitter at @vishal4c and via email at [email protected]