AnubisDAO Investors Lose $60 Million Under Unclear Circumstances
A recent crypto project AnubisDAO, which raised $60 million overnight seems to have lost the funds under unclear circumstances.
AnubisDAO was promoted as a fork of OlympusDAO — a cryptocurrency backed by the assets in its treasury. It was first announced on October 28 with the launch of a Discord server and a Twitter account, which ended up only making a few tweets. The supposed fork was themed around Anubis, an egyptian god of death that has a dog’s head, a branding similar to other dog-themed memecoins.
Even though the project didn’t even have a website, investors jumped into the token sale, with $60 million in ETH invested into it.
The token sale was supposed to continue, with more investors putting in ETH and receiving anubis tokens (ANKH) in return, for a 24 hour period.
However, at 11:58 UTC — approximately 20 hours into the sale — the liquidity in the pool (which enables investors to buy and sell the tokens) disappeared. The $60 million in ETH that had been put into the token sale so far was then sent to a different address.
Liquidity being removed was a bad sign, and it getting removed before the sale ended was an even worse sign. Both pointing toward either a rug pull (where the team disappears with the money) or that the money was stolen by another party in some kind of exploit.
Since the money was taken, the price of the ANKH token has effectively gone to zero because there’s no liquidity to sell into. The chart below was originally on the Copper website — where the token sale took place — but has since been removed.
Twitter sleuths found a series of transactions that connected the wallet that received the funds to a Twitter account named @Beerus. The Twitter account has since then been deleted.
The owner of the Twitter account claimed — under an alternative account — that they might been victims of a phishing attack. They shared a screenshot of an email from someone pretending to be crypto investor 0xSisyphus that contained an attachment, which could have contained malicious code.
recieved this email which seemed to have been the issue
