Original Title: "Ankr Attack: Arbitrageurs Profit More Than Hackers, Hackers Play "Performance Art" with Weasels"
Original Author: Loopy Lu
Today, the deployment key of Ankr is suspected to have been leaked, and 10 trillion aBNBc tokens have been minted. The liquidity of its trading pool on Pancake has been drained, and the price of aBNBc has almost dropped to zero.
Unlike previous attack incidents, this attack incident has many funny "stories": the arbitrageurs made far more profits than the hackers (assuming they are not the same person), the hackers issued the FuckBNB meme coin and engaged in "performance art", aBNBc continuously increased its total issuance to an unprecedented amount, and so on. The attention brought by the subsequent development of this attack incident has even surpassed the attack itself.
This morning, hackers gained deployment privileges for Ankr and launched an attack on the project.
According to on-chain data, 100 trillion aBNBc Tokens were minted and sent to an address starting with 0xf3a4 in a transfer transaction. The transaction can be viewed at this link.

After a huge amount of Token was issued, some aBNBc was left in the wallet, while more Tokens were thrown out for profit. The hacker transferred 1.125 BNB to their address as gas fee and started selling aBNBc, exchanging a total of 4,050,500 USDC and 5,000 BNB. The 4,500 BNB profit was exchanged for 1,293,087 USDC and 900 BNB was deposited into Tornado.Cash. The attacker then cross-linked all USDC into Ethereum networks Celer Network and Multichain, and exchanged all 4,684,156 USDC for 3,446 ETH. Due to the significant drop in ANKR price, the current shorting ANKR return rate is 53.25%.
The security team of PeckShield has discovered that there is an infinite minting vulnerability in the aBNBc Token contract in the Ankr hack incident. Although the mint() function is protected by the onlyMinter modifier, there is another function (with the func.signature of 0x3b3a5522) that can completely bypass the caller verification to obtain unlimited minting permission.
This attack resulted in the depletion of the liquidity pool of aBNBc Token, causing a halving of the coin price. The hacker profited approximately 5 million US dollars from this attack.
If the matter ends here, this is just another "ordinary" security incident in the bear market. However, the "arbitrageurs" have caught up with the opportunity.
When aBNBc was hacked to zero, a user ( 0 xaab 2 ……dfc 3 ) purchased over 180,000 aBNBc with 10 BNB and mortgaged aBNBc on the lending platform helio to borrow over 16 million stablecoins HAY. (Note: HAY is a decentralized stablecoin based on BNB, which can be minted by depositing aBNB-LP. ) The official team has stated that they have discovered the vulnerability and will immediately notify the community after obtaining more information.
Arbitrators sold Hay for over 15 million BUSD, and the Hay liquidity pool was emptied. As a decentralized stablecoin, the price of HAY was once severely unanchored, falling to a low of about 0.21 USD, but it has gradually rebounded and is currently priced at 0.70 USD.

After hackers made a profit of $5 million, arbitrageurs made a profit of $15 million from lending platforms, which is much higher than the hackers' profit.
The last time there was a "arbitrageur's profit exceeds hacker" incident was in the pGALA event. In the industry, the true identity of the "arbitrageur" has aroused suspicion among investors. Users have made speculations about this mysterious figure, with some suspecting that the arbitrageur may be just another address of the hacker.
However, the development of the situation far exceeds everyone's expectations. Although the attacker's profits have been anonymously transferred by Tornado, the arbitrageurs seem to be unfamiliar with on-chain operations.
On-chain data shows that an anonymous arbitrager transferred their profits of 15.5 million US dollars to Binance through an intermediate address (0x4c......2757).

Although this set of profit-making behaviors cannot be called "hacking attacks", it is in a sense "improper gains".
Next, CZ said that Binance suspended withdrawals a few hours ago.
In this incident, there were also many amusing "anecdotes".
This afternoon, CZ stated on Twitter that the preliminary analysis of the hacker attacks on Ankr and Hay is that the developer's private key was stolen, and the hacker updated the smart contract to a more malicious one. The security team's investigation also came to the same conclusion. Some security teams found that multiple different calling addresses caused an increase in Token issuance. This has an interesting consequence: the hacker address of the Ankr attack may be the largest in scale among all previous attacks.
BSCScan's tag display, Ankr Exploiter's logo, and even the numbering have reached more than fifty. The number of attacker addresses is staggering.

Even more bizarrely, due to multiple calls resulting in multiple issuances, the quantity of aBNBc issued is no longer the original 10 trillion coins.
The on-chain data shows that the total supply of aBNBc has exceeded 10 to the power of 60.

More precisely, its supply is 115, 792, 089, 237, 316, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000, 000 coins.
After the attack, hackers were not satisfied with the "small" profits from Ankr and were committed to further expanding their profits.
On-chain data shows that the attacker created a token called "Fuck BNB" and provided 15 ETH on Uniswap V2 to establish a liquidity pool for it. However, security firm Go+Labs later stated that "Fuck BNB" token is suspected to be a Ponzi scheme, and users should be aware of the related risks.
This afternoon, Binance announced that it has frozen about 3 million US dollars transferred by hackers to the trading platform. BNB Chain also stated that it has noticed the Ankr aBNBc contract was attacked by hackers earlier today, and the attacker's address has been blacklisted.
Ankr has also responded to the incident. It stated that it has contacted DEX and informed the trading platform to block relevant transactions. Ankr is currently evaluating the situation and will reissue the Token. In addition, Ankr guarantees that all underlying assets of Ankr Staking are safe and all infrastructure services are not affected. Ankr is currently drafting a plan to compensate affected users.
Ankr has provided four tips to its users: 1. Do not trade; 2. The liquidity provider for aBNBc Token has been preserved, please remove it from DEX; 3. Ankr will take a snapshot, and users can wait for further updates; 4. aBNBc will be reissued.
The stablecoin trading platform Wombat Exchange has announced that it has suspended the BNB pool, as well as the exchange, deposit, and withdrawal of BNB, BNBx, stkBNB, and aBNBc. Previously, Wombat had already suspended the aBNBc pool and the HAY pool.
In this incident, the losses of the lending platform were far greater than Ankr's, but as of the time of publication, HAY has not made any further response to this incident.
Original article link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia