🚀 DEXX Hacker Transfers Significant Funds Amid Ongoing Asset Exchanges
#DEXX #hacker #Ethereum #TornadoCash #blockchain #assetexchange #cybersecurity #cryptovulnerability #ETH #BNB
According to Foresight News, recent monitoring by MistTrack has revealed that the attacker involved in the DEXX incident is actively exchanging assets and bridging them to Ethereum. As of now, the address beginning with '0xFFB9' still holds a balance of $620,000, distributed across Ethereum, BNB Chain, and Base Chain.
The hacker has successfully transferred 6,212.4 ETH to Tornado Cash, a privacy-focused platform known for its ability to obscure transaction trails. This movement of funds highlights the ongoing efforts by the attacker to manage and potentially obfuscate the stolen assets. The use of Tornado Cash suggests an attempt to make tracking the funds more challenging for investigators.
The incident underscores the persistent vulnerabilities in blockchain systems and the sophisticated methods employed by attackers to exploit these weaknesses. As the situation develops, it remains crucial for security teams and exchanges to enhance their monitoring and response strategies to mitigate such risks effectively.#DEXX #hacker #Ethereum #TornadoCash #blockchain #assetexchange #cybersecurity #cryptovulnerability #ETH #BNB
🚀 Futureswap Contract on Arbitrum Faces Reentrancy Attack
#Arbitrum #Futureswap #ReentrancyAttack #BlockchainSecurity #CryptoVulnerability #LPtokens #SmartContractAttack #CryptoLoss
According to Foresight News, BlockSec Phalcon has reported that the Futureswap contract on Arbitrum has been attacked again, resulting in an estimated loss of approximately $74,000. Although the financial impact is relatively minor, the incident has highlighted a new vulnerability: a reentrancy flaw. The attacker exploited this flaw through a two-step process involving a three-day cooling period to steal funds from the protocol.
In the first step, during the minting phase, the attacker took advantage of the reentrancy vulnerability by re-entering the 0x5308fcb1 function before the contract could update its internal records. This allowed the attacker to mint a large number of LP tokens disproportionate to the actual assets deposited.
In the second step, after the mandatory three-day withdrawal cooling period, the attacker executed a withdrawal, burning the illegally minted LP tokens to redeem the underlying collateral. This effectively enabled the attacker to extract assets from the protocol and secure a profit.#Arbitrum #Futureswap #ReentrancyAttack #BlockchainSecurity #CryptoVulnerability #LPtokens #SmartContractAttack #CryptoLoss