Crypto Sleuth ZachXBT Claims Second Bounty After Submitting \'Definitive\' Evidence of the KYC-Deposit Address Used by a Hacker to Cash in on the $235 Million WazirX Hack
- WBOYOriginal
- 2024-07-19 11:59:35930browse
Arkham posted the bounty this morning offering 5,000 ARKM (~$8200) to anyone able to identify the KYC centralized exchange deposit
Crypto sleuth ZachXBT has claimed his second bounty after submitting ‘definitive’ evidence of the KYC-deposit address used by a hacker to cash in on the $235 million WazirX hack.
Arkham posted the bounty this morning offering 5,000 ARKM (~$8,200) to anyone able to identify the KYC centralized exchange deposit, the exploiter’s identity, or help return stolen funds.
Indian crypto exchange WazirX was hacked on July 18 and funds, including $100 million in SHIB and $52 million in ETH, have reportedly already been sold.
ZachXBT told Protos that he was already following the WazirX hack and that submitting evidence for the bounty was as simple as exporting a graph. He added that it wasn’t super difficult to identify the relevant centralized exchange deposit address.
He also shared his method of tracking the exploiter’s transactions, noting that the WazirX hack “has the potential markings of a Lazarus Group attack (yet again).” Blockchain analysis firm Elliptic shared similar suspicions that it could be linked to the North Korean hacking collective.
ZachXBT previously claimed a $150,000 bounty from Arkham that asked for evidence identifying the creator of the Donald Trump-themed DJT token. Indeed, he submitted evidence that Martin Shkreli was DJT’s creator which Arkham accepted as ‘definitive’ proof.
Got a tip? Send us an email or ProtonMail. For more informed news, follow us on X, Instagram, Bluesky, and Google News, or subscribe to our YouTube channel.
The above is the detailed content of Crypto Sleuth ZachXBT Claims Second Bounty After Submitting \'Definitive\' Evidence of the KYC-Deposit Address Used by a Hacker to Cash in on the $235 Million WazirX Hack. For more information, please follow other related articles on the PHP Chinese website!