PANews reported on October 2nd that ZachXBT monitoring revealed another unusual movement in the attacker's address (0x8Da...Ea30) linked to the Coinbase security incident. The attacker initially exchanged approximately 5 million DAI for 5 million USDC and, after holding the USDC for approximately 35 minutes, transferred the funds via a cross-chain bridge. ZachXBT noted that Circle appears to have failed to freeze the USDC funds within that timeframe, with some of the funds reportedly being transferred via Circle’s official Cross-Chain Transfer Protocol (CCTP).PANews reported on October 2nd that ZachXBT monitoring revealed another unusual movement in the attacker's address (0x8Da...Ea30) linked to the Coinbase security incident. The attacker initially exchanged approximately 5 million DAI for 5 million USDC and, after holding the USDC for approximately 35 minutes, transferred the funds via a cross-chain bridge. ZachXBT noted that Circle appears to have failed to freeze the USDC funds within that timeframe, with some of the funds reportedly being transferred via Circle’s official Cross-Chain Transfer Protocol (CCTP).

ZachXBT: Circle did not freeze the funds in the Coinbase hack, and the hackers have now transferred them across the blockchain.

2025/10/02 18:36
1 min read
For feedback or concerns regarding this content, please contact us at crypto.news@mexc.com

PANews reported on October 2nd that ZachXBT monitoring revealed another unusual movement in the attacker's address (0x8Da...Ea30) linked to the Coinbase security incident. The attacker initially exchanged approximately 5 million DAI for 5 million USDC and, after holding the USDC for approximately 35 minutes, transferred the funds via a cross-chain bridge.

ZachXBT noted that Circle appears to have failed to freeze the USDC funds within that timeframe, with some of the funds reportedly being transferred via Circle’s official Cross-Chain Transfer Protocol (CCTP).

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact crypto.news@mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.