Group Finance hacker returns M to related tasks after exploit

Group Finance hacker returns $7M to related tasks after exploit

by Jeremy

4 tasks have obtained some $7 million value of tokens from the hacker behind the $14.5 million Group Finance exploit on Oct. 27. Over the weekend, the attacker confirmed in a sequence of messages that they might hold 10% of the stolen fund as a bounty and return the opposite tokens to the affected tasks.

The exploiter — a self-described “whitehat” — drained property from Group Finance by means of the Uniswap v2-to-v3 migration. As reported by Cointelegraph, liquidity from Uniswap v2 property on Group Finance have been transferred to an attacker-controlled v3 pair with skewed pricing, defined the blockchain safety agency PeckShield.

The stolen funds included USD Coin (USDC), CAW, TSUKA and KNDA tokens. Among the affected tokens, equivalent to CAW, suffered steep value declines because of the exploit and subsequent liquidity crunch. 

On Oct. 30, Kondux, a nonfungible token (NFT) market, introduced it obtained 95% of the stolen funds, or 209 Ether (ETH), whereas Feg Token recovered 548 ETH. Tsuka’s blockchain protocol additionally confirmed receiving over $765,000 value of the stablecoin Dai (DAI) and 11.8 million TSUKA. Caw Coin — the largest sufferer of the exploit — obtained again $5 million value of DAI and 74.6 billion of its native token, CAW.

On Twitter, the protocol urged the hacker to get in touch for a bounty fee. In accordance with Group Finance, its sensible contract had been beforehand audited, and builders had briefly halted all exercise on the protocol. The corporate was based in 2020 by TrustSwap, which supplies token liquidity locking and vesting companies to challenge executives. The protocol claimed to have $3 billion secured throughout 12 blockchains.

The exploit adopted the Mango Markets assault on Oct. 11, when a hacker manipulated the worth of the platform’s native token, MNGO, to realize greater costs. The attacker then took out important loans in opposition to the inflated collateral, draining Mango’s treasury.

After a proposal on Mango’s governance discussion board was accepted, the hacker was allowed to maintain $47 million as a “bug bounty,” whereas $67 million was despatched again to the treasury.