Post Mortem
Introduction
On April 15, the $GB token on Base Chain fell by more than 99% in just a few minutes due to a compromised deployer wallet. After three months of thorough investigation, we have identified the hacker, understood the mechanics of the hack, and gathered insights to prevent similar incidents in Web3.
Grand Base was founded by a single individual and had one lead developer, who initially introduced himself as ‘Anan Phoon,’ claiming extensive experience in DeFi development. However, our research revealed that ‘Anan Phoon’ is a fabricated identity. The individual, who also goes by various aliases including ‘Anan,’ has been identified as the mastermind behind the GrandBase hack. This person has been impersonating other developers and has connections to the DPRK/Lazarus hacker group, as uncovered by Symbiotic_bnb, a Binance security researcher. The CTO informed us that he might have a clue about the identity of the “hacker” by claiming his personal wallets were compromised after disappearing for over 7 hours after the hack, this has given us a list of addresses to track and study the case, which we will detail in this article.
Modus Operandi
To understand their methods of infiltrating projects, refer to this post by Zachxbt about the Munchables hack: [zachxbt’s post on the Munchables hack](https://x.com/zachxbt/status/1772843238539325947).
Aliases and Accounts
Anan has used several aliases and accounts on Telegram, GitHub, and Twitter:
Telegram Handles:
- @elcrazy_jack (active) (https://t.me/elcrazy_jack)
- @blockchainexpert2019 (inactive) (https://t.me/blockchainexpert2019)
- @ananphoon (inactive) (https://t.me/ananphoon)
- @oxdiehard (active) (https://t.me/oxdiehard)
- @genie8848 (active) (https://t.me/genie8848)
- @grandbase_tech (active) (https://t.me/grandbase_tech)
- @dripdrop95 (active) (https://t.me/dripdrop95)
GitHub Accounts:
- blockchainlover2019 https://github.com/blockchainlover2019 matches the Telegram handle @elcrazy_jack.
- ilesoviy https://github.com/ilesoviy (0xdiehard): Similar style to the Munchables dev.
- BlockchainCrazy95 https://github.com/BlockchainCrazy95
-EthereumLover2020 https://github.com/EthereumLover2020
Twitter Account:
- [Jack Poon (@JackPoon228)](https://twitter.com/JackPoon228)
Additional Information
- GrandbaseTech uses the following number: +1 512 333 1713
— Linked to two individuals:
— A doxxed person named Ch** Lo**** in Texas, USA, and an Asian individual (likely from Hong Kong).
— Ch** Lo**** is a software developer at Persona, a leading KYC/AML company.
— He is likely innocent, targeted because of his sensitive work history.
— The phone number has likely been in “Anan’s” possession since 2019.
- Pseudonyms and Accounts:
— Uses many pseudonyms, including Jack and Ryan.
— An old Telegram account linked to the username @dripdrop95.
— Multiple GitHub burner accounts.
- Dox Information:
— The dox information provided by Anan is unclear and unconvincing.
— No records of an Anan Phoon / Anan Poon in relevant locations.
— Claims to be an MSc student at the University of London, but no supporting records found.
— The photo provided does not match criminal databases or facial recognition software records.
- The evidence suggests organized crime rather than a lone rogue hacker.
- Binance Security confirms the transactions are linked to the Lazarus group.
- Anan’s computer was implicated in the breach.
- it’s a large-scale operation and it’s been planned for a long time and has repeated itself now with Grandbase after Ratio Finance.
Binance Security Guard has indicated that the transactions made by the exploiter were linked to the Lazarus group. The source of these transactions was traced back to Anan’s PC, suggesting that this incident is likely part of a larger organized crime operation, rather than the actions of a lone individual from Hong Kong or Canada.
Shared Wallet and Fund Flow Analysis
A team wallet, shared between the CTO and other developers, identified as 0x48a2450ae9eD6b035b75f715f226CEd05CdA5A0A, exhibited an outward flow of funds. The analysis shows that two HitBTC deposit addresses were one of these funds’ final destinations. This pattern is consistent with how the CTO/hacker transferred some of the hacked funds from his personal wallets to HitBTC deposit addresses, as detailed in the report.
The fund flow from the shared wallet is as follows:
1. Initial Funding Address: 0x79f916dc840eBb2559C96f3865224057a62B6895
— Transaction Hash: 0x6539834d709626a8b5d0ea72d3af1c2aafac22e0b6b8f881672e30c81f840927
2. Subsequent Funding Address: 0x40E7004fdCdB8ADCc7791b40cEE3Ba0FC66C1dC2
— Transaction Hash: 0xaa7250237aa2c82d1d96e0c80519513b2f08c2c2c08cf430ef03e88c6ae41334
3. HitBTC Deposit Addresses:
— Address 1: 0xF1A02392e00d112f92FE6df513051dD22138F501
— Transaction Hash: 0x2570efd585eb0ab8a7b47fdd9468dc1c4951165357af67b05c19881151ab07c7
— Address 2: 0xfCAfcC0D7bB81edFDE5835650B574fF44F61B154
— Transaction Hash: 0x5f71b2d7f84fa4569f6bf8a48b05fa0065848cb54b08da441a4d95fbf4285980
All these transactions occurred in January before the exploit, except for the deposits to HitBTC. Notably, none of these wallets were reported by the CTO as being “compromised.”
Intel According to Hacker Wallet
Hacker Wallet Details
Wallet Address: 0x633a571dE0eAD533C4677790815BB074CAB6F562
This wallet was used to steal funds from the following three wallets, which were located on the devs/CTO’s computer:
1. Wallet Address: 0x1E3b54a4149aF3e0f0505B1FaD658b3a3bCFa110
Transaction Hash: 0x655acf69dfdede50f2f6a406e09790d7a978acb35f0f6a8179eea51fd90bdbaa
2. Wallet Address: 0x75c54Df9F8c624096E7eCBc3F3992C5C60BC7ED5
Transaction Hash: 0xa208b9adf1e5be6fd8ccad0e1304cd425230cd76e55b91a6acdd83b9572ebad8
3. Wallet Address: 0x3F796eA0f35602543Ef562Cc236459968B362Fce
Transaction Hash: 0x800d77113c169eb76974f40d52dc815fbd23e183911e00fe2f65e090e59f0189
Current Holdings and Transfers of Stolen Funds
A portion of the stolen funds is being held in, and was recently sent to, the following wallets:
1. Wallet Address: 0x90dD42030C6d67765133669596d2b36C11F5668D
Transaction Hash: 0x5530e8b84ac7da36866c063db4e86ac4072a345f776a4a6f7430ef1c00277157
2. Wallet Address: 0x8ddaCF66561017d77acf09b0acB8f263900EFA5e (HitBTC deposit address)
Only one wallet has sent funds here.
Transaction Hash: 0x02bb56fcf602cdae0a55bf41ed83394cfd8831aceef5d0fd9cb96bc8d4e4e621
3. Wallet Address: 0xAeeB73645Defd47d6653D6D0069171Fc24Add99D
Transaction Hash: 0xc0032e5974e577384af34f6c9a949b1fbc9daa1ed06458a7e02fbc7eadce6d7e
The hacker wallet, 0x633a571dE0eAD533C4677790815BB074CAB6F562, sent funds to the HitBTC deposit address, 0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02 (Transaction Hash: 0x368a9b87fa7c11d25fbcd0617e55d97965c3a44031e2b1b5147ef1a535fae664). Refer to the picture above for details.
This HitBTC deposit address, 0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02, has received inflows from 13 different wallets in addition to the hacker wallet mentioned. Most of these wallets appear to be connected, each having made a single transaction to this address.
Some factors about the connecting wallets that are deposited into the HitBTC deposit address:
The majority ofthem utilized exchanges such as Coinbase, Binance, HitBTC, OKX, Changenow, Bitget, Moonpay, Changelly, Crypto.com, Changelly, and Gate.io, with the majority of important interactions having been with Binance, Coinbase, HitBTC & Blockchain.com.
- The report will be focused on close connections via exchanges utilized and wallet connections.
Connections of the address that first sent funds to the HitBTC deposit address 0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02:
- 0xf15a79362bdbd56Af8ff9C513C6F95d3d4253201 was the first address to send funds to that deposit address (Txhash: 0xd97357124c0d5659637d8d7267c5eb21a88554521542282dab8b61f51bae24d8).
- 0xf15a79362bdbd56Af8ff9C513C6F95d3d4253201 was first funded from 0xF3901D6d230C2B0F19db92cC06C289258c1C3CbD (Txhash: 0xeffae592da83cf8550a5668aeac706de2f0ae21a3d0cfcba35c254fb01bdcc15).
- 0xF3901D6d230C2B0F19db92cC06C289258c1C3CbD has deposited funds into seven different Blockchain.com deposit addresses:
— 0xCF194094a0966242cF9158B86f8cCf1A558063F3 (Txhash: 0xfc32fe825eb26281d7712c436d525a9067fb60acd934bab945cce8162ef8cf1c)
— 0x0BB7bD70fA020580C41FE1d297c58d494cE58cF7 (Txhash: 0x4d241543431634b0cc17a1bf815be67dd7369c973379bb0c7e63824697c914bb)
— 0x90c779ADFDE00C2CA938D64b41534d8E3D2faCDC (Txhash: 0xbdadcce4dbea82579695251b29dcef680b21657d8ae8bebfc09ee45ca5d280b5)
— 0xA2EFbCc32F02D346295489ad5406f4e98E253f9E (Txhash: 0x51c583f8400572292ab62b27a108a2fdbbf916dfb74f6faef81e4eeefebdd3b1)
— 0xbE93Acc28B0e6989fEA4b9092AC8A21F465752F6 (TXhash: 0xef9c8b4715cfc9a6ea18dc68bd01d9b90d91d0e6a9d0a4feb1c10e8260220c74)
— 0x3A027e4efA5cf71903960b0C1ecE4A72B3D43F32 (Txhash: 0x32d1551f02ea0de35f70d12492f5414e25b18a9371ee5f1e4df6713d357fd56a)
— 0xF11a9f68e5f861B89625CeC2D45DAF2C6c382CF9 (Txhash: 0xe300738a254d91a8670d6c8583b0a98bf7e5d307c10366b8a9c56c05dc4be337)
Other deposit addresses that 0xf15a79362bdbd56Af8ff9C513C6F95d3d4253201 has sent funds to:
- OKX deposit address 0x4d391b4363f4d0cd6309d314e5753f67039cb0fb
— Txhash1: 0x16191dae2f568f07ca60322a42424e583406d1b6d59d2aac3ec1bcc2b445ac2d
— Txhash2: 0x8d8ddf253354348ac9167273d843d096301e62365558ee5cb3490c01aaaf8569
— Txhash3: 0xc8d39a3dfa7b2c99c6459fb1f9a8b1a823eb23c3922e4e881c1933d6a1939102
— Txhash4: 0x9492c2558885cbd89da816fc3137ef167488deac503ebaf33ec06aa5217bb6dc
— Txhash5: 0xab6823c155a13ef783c74b1e141bbb020e59c725e31aed7b203446b6340b8481
— Txhash6: 0x11b52e10bdbf78b6fcb86a21e691fcdea944d6427de90bdf0d69c8f54afab777
- Binance deposit address 0x0aB7dce2F52Cdb54b6Fa5C22E3c843D86A83cEaF
— Txhash: 0xe6a011801805d84c2812c74853f968109dbabb19f7ca7a99abcfb8ba6158debe
- Binance deposit address 0x20E3A9CF9f2d4773dE24Fb50B1EfF25fed70aCC3
— Txhash1: 0x4eec8529d342fccc5b8e51fa488d44dd5573a17cec6aadd244e6b4ef425a4f30
— Txhash2: 0x51fa88b9bef4fae2f4ecf416ca0688226c0f10c48aa7febf5d41ecb48aebd2c0
— Txhash3: 0xe5a4e436b88895d5cc492e0d5ebdd40d9ddc80e65e29bea44d576a867162d271
— Txhash4: 0x71e5a53ae458f1f83b4e6ba84805945d27fc919486dc7ac58200e161ca49ec95
— Txhash5: 0x1bedfcef440f3ba20e39965b36a67cbdfb22d00fb308ec51aaca2a33eb3d4707
— Note: The same deposit address was used by a hacker during an Upbit theft (see article: https://medium.com/sentinel-protocol/identifying-exchanges-affected-by-stolen-upbit-eth-41e6e5db6962)
- HitBTC deposit address 0xE217A0C01f39a1D0b26321D31e996496700fB02F (Txhash: 0x5a8f72e64320193af36e8f30884213279b458e22bb84aeeb2c35fa99120dbee3)
- HitBTC deposit address 0x23C683DbE656d7F030d50d6Cd00208e5dB36CF84 (Txhash: 0x8f93d10e9bb248c6c90a7178e6383d94b34e954f38129fff4211fc6920c4541c)
- HitBTC deposit address 0xa4B907178C2906aE8AD859d286F4324773B5846C (Txhash: 0xbf15585de83ed8a391bb559b4228c579e1eec86f05e9eb87c6a6b964cc4cce95)
- HitBTC deposit address 0xC861303aaE71050790a1a0BB5b8d077507b8c1B3 (Txhash: 0xe96248dc15ab9abbcc25a4c14510cf409e53c8ce90e84a8f7d93c73693d6c138)
- HitBTC deposit address 0x7eF06D5DC68e554e2fb7C731B333d970A8403F80 (Txhash: 0x7877f6bd227f9283a1448b7c34ae936620edcbb2fb07a5d7b57602f3c9797a9a)
Wallet connections of 0xF3901D6d230C2B0F19db92cC06C289258c1C3 Txhash=0x25617d7fc6713bf97f09e5f41b7266eff022f1a9e03 a43696aa0e1a0f160bf58
- As we can see in the above picture, 0x072c9B942aaFB8a10EA04c7fFF42b0FcaDD03e7a has also served as an intermediary wallet for 0xF3901D6d230C2B0F19db92cC06C289258c1C3CbD and 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E, having sent funds to 0x3e8 twice and 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4, which first funded 0x072.
— Txhash1: 0xd2434f576c727e54a212b53d778d161b99a1d5dc6921589ca5516f793bc415c2
— Txhash2: 0x73a2e339f5c323c218774438201709b9b669a0d648ca410520e361bf3d6c7425
— (0x3e8 outflows txs): Txhash: 0xb4270588c51c6adaf9b596775b18e66e9df494172676840cb3da1d154c11acee
— (0x72 first funded tx)
- Another strong connection between 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E and 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 is their intermediary connection via wallet 0x20D382E6e84333062eEC7Ba9412d64dcFaa3b088.
— Txhash1: 0xb0a0569ec53e3f687c978a3b8b193cdcc062896e7172413f8a4bd68359f53a13
— Txhash2: 0x8a567e534b94051426a5665892f6a8071650804349c5b8594d5afdafdb4efc6b
- Wallet connections of 0xF3901D6d230C2B0F19db92cC06C289258c1C3CbD and possible lead/suspect pt.2:
— 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4’s largest outflow to a deposit address was to HTX deposit address 0xd5a0A2361fdcdeE1fef0c65fF94aA70b1E8c2079, and it has only sent funds to an HTX deposit address once.
— Txhash: 0x09f96ed86db092f18abcd5e68950479f9428fd5752fcf5a7b36f7e4a703220e7
— 0xd5a0A2361fdcdeE1fef0c65fF94aA70b1E8c2079 HTX deposit address’s highest amount of inflows came from 0xB2181a90E0eE0de4Dc798559eDF76e7fB054834e for 13 inflows.
— Txhash: 0xea53f57c0cbc3abc963abc57d34afd5fb3d273604783896423db4e4423fc94cd
-0xB2181a90E0eE0de4Dc798559eDF76e7fB054834e has had seven inflows from 0x43Bf7BcF64C501D5f4632d7f1cCE6779aeA3c8b3 aka labeled wallet “SpecialsK” and was also the first EOA to send funds to it Txhash=0xabc6ed3b289214c8c91233512f4230b01b41d157 291124885a820fa91dd8edcb
-0x43Bf7BcF64C501D5f4632d7f1cCE6779aeA3c8b3 aka “SpecialsK” also is connected to and owns the Unstoppable domain “klauss.x” (The unstoppable domain will serve as a reference to another wallet connected to the Hitbtc address the hacker has sent funds to)
- 0x43Bf7BcF64C501D5f4632d7f1cCE6779aeA3c8b3 had received a “transferfrom” (of a BAYC NFT) from the deployer wallet (0xd40135Df587ab99282A52b17F5d73269e650942f, aka FurBrawls) of that project.
- Additionally, 0x43B had purchased two Super Bunnies NFTs.
- Lastly, 0x43B’s profile picture on its OpenSea profile is that of a Super Bunny.
The BAYC sent to 0x43B was sent due to a giveaway he had won
Also, we have found that 0x43Bf7BcF64C501D5f4632d7f1cCE6779aeA3c8b3 happened to be included in this PDF. Use urlscan to view https://pdfcoffee.com/2-286-pdf-free.html](https://pdfcoffee.com/2-286-pdf-free.htm
Discord id and username= 714771241063546970, .klauss
Exchange Connections
Between 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 and 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E:
Get Reflect’s stories in your inbox
Join Medium for free to get updates from this writer.
- Both wallets have inflows originating from FreeWallet.
— 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4:
— Inflow from FreeWallet: 0x7eD1E469fCb3EE19C0366D829e291451bE638E59
— Txhash: 0x4bc57d161b134faacb8d21dcf1e631d32ded98506dbc7635d19bb77d87ce27c3
— 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E:
— First funded by: 0xb7A90404C5ad22e172E7B5769d540A4133d453C3
— Txhash: 0x49ab47facc16e2eeea20bd07e44157976ef008913b5e6eef749ac6a700f5e756
- Funding Chain:
— 0xb7A90404C5ad22e172E7B5769d540A4133d453C3 was first funded by: 0x4f40b357b642Ab89744fFE3e77859D03A10bdC00
— Txhash: 0x75d96ce7c54e7657838705acb6056081863797b89a9c0e767b7dc9ad321b5c09
— 0x4f40b357b642Ab89744fFE3e77859D03A10bdC00 was first funded from FreeWallet: 0x7eD1E469fCb3EE19C0366D829e291451bE638E59
— Txhash: 0xb46773efd758779af561cdcd604cce05b00df2b04de9ef9e8407c380f9a123a8
Pictures of the above transactions are included below.
Both have sent funds to Binance deposit addresses, even having a shared deposit address 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E to 0xe7a7824948a7FEa0c393f38178bEA801051AE2A6= Binance deposit address (seven deposits made) Txhash=0x0795482928b7351dd8189384657b08c5a621a96 e200eced20006744c998ad51b
0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E to 0x934f8F7c95EB317e318E09448464d5b3997a2Ad9= Binance deposit address (Five deposits made) Txhash=0x52f753b8eaa8846f9c14cff3eaa06fb483a5e875d1 88383d53026ec2063ec7e9
Binance Deposit Address Connections
Between 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 and 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E:
Shared Binance Deposit Address: 0xA242753552bb7be0cBf39719E99aa3b774a9C6eA
- Transactions from 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4:
— Txhash1: 0xcb2341a3f84152441138adbba8c1c952f52140aa80a0f9cc3b3d86161a336969
— Txhash2: 0xbc0054286f57bcf3db1cf54d26950aa42de84dda731efce95274b8dbc3459389
- Transactions from 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E:
— Txhash1: 0xcb4c8fa7f28c5c11329f97a580ad7b66d982ee7a32adeab46e0e669e1d0f84fe
— Txhash2: 0xfdbbfc6cefa82cf1aad46ee184df5426b4ed836d9988224047835463fdc80b1d
— Txhash3: 0x36d6cd49266c34eedf76a63697822aac215c7e3061119fd2e089145b5b3c68a3
Connections between 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 and 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E
Coinbase deposit address connections:
- 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 to Coinbase Deposit Address:
Address: 0xfC5066a139432d0021178fF54bA813f95A327bCf
— Txhash: 0x4c845058cbbdeaa2603acc754c8f9afe91511def293809708a531abacfdebfad
- 0x3e8E85A28738B56E15Bd35773f92639e38f9CE1E to Coinbase Deposit Addresses:
Address: 0x25d306Ac71878E663D3c226738c92FAFe4E09094
— Txhash: 0x28801c96b14bcc55c71e1483d7ed7b0e5ff4f681e20bedb1165e91d5497d558d
Address: 0x47A4F0b1EBC54bCd9A53AaA02570748C1767d7fC
— Txhash: 0x55df47839387b8ca2a9ef1e1b37434d37c92a02ae7262deb60b5d71738788593
Address: 0xAed0BE82E3f9814566fD84778d1Fba99b2158a43
— Txhash: 0x41d8a72df0191239944453fe5cdbc3fec20a35bbeaaea8666c6cdc4acf7cc839
Blockchain.com Similarities:
- 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4 received funds from Blockchain.com:
— From: 0xC88F7666330b4b511358b7742dC2a3234710e7B1
— Transactions: Eleven withdrawals
— Txhash: 0x9ff45de1c4c69f185906cf15ff39bc08535f9bf5d8230d2d9ad070b18c66d839
- 0xF3901D6d230C2B0F19db92cC06C289258c1C3CbD received funds from Blockchain.com:
— From: 0xC88F7666330b4b511358b7742dC2a3234710e7B1
— Transactions: Seven withdrawals
— Txhash: 0x8fea88a427755ff5de74c4c090d64a424a5661da8224d53e43abfad3b3d82205
See below images:
Inflows into blockchain Deposit Addresses for 0x24B8AE2f5371E88466DF7eeE6036Cb3495dC23F4:
- To: 0x3214B7A47f853D6C48f091f39f770e25f5C4c502
— Txhash: 0xe7097cafacee0aa7b6156802e5f4c42acd2d36623b33a7b6c5749c1b4d5356ce
- To: 0x7cbB658040a1c90d711d93442F06Fd1Ae344487d
— Txhash: 0xcfdfd7e8486c241ac22b5053fe003e20dca1ba3b84879e854e20079cda8bb770
- To: 0xB531eBcD8f651d6dfa4CDcDc4164A012BF6c8eC8
— Txhash: 0xaa155238baa5315a27a9f85a8814ebd7f4f2d18d077124d726747fc831fc71d7
Connections to HitBTC Address 0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02:
- Most active wallet: 0xC9a2e37b91bc81453489B2bB85Ec52E81C5bbbc9
— Excluded due to unrelated casino gambling transactions.
Other Active Wallets:
1. Wallet: 0x230C67a5970Dc736d63c889CaCde226d5F370AD6
— Inflows to HitBTC deposit address (0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02):
— Txhash: 0x8828b93ac995c093dfbad383089107dfa91d1c2e4346b271fb657d313fa8fe19
— Received funds from HitBTC exchange 24 times:
From: 0x59a5208B32e627891C389EbafC644145224006E8
— Txhash: 0x9fd3b3f8fa6c27667f58bc7f4e0494be6c324c205efaf63337b0eb7a6b36d435
2. Wallet: 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
Inflows to HitBTC deposit address (0x71C1eb74F88146fC8DdD11Be6491Efdfe0A05d02):
— Txhash: 0x2856dfeefe0b747f71315128d0c798a9c53fb610382b261af9eba1fa4a1643b5
Received funds from HitBTC exchange 11 times:
From: 0x59a5208B32e627891C389EbafC644145224006E8
— Txhash: 0x509d693f5e59dde2ec9a0ae32a4fbbf1a6b1756798a893f9f66e4e59c85dee4c
Hitbtc Deposit Addresses:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0x69D2fB1D0B72BcD0A9C8793EB811e6d1D0A65454
— Txhash: 0x33e00a362728353db3d3b7d1d9ba014a39d90c9997ee792e15f5d52ed3c1e989
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0xe181a1F9a75591D33845108a5eFeD24b072e500C
— Txhash: 0x3613bd47190226845d12159ccca2e744ae1cf3298a2eca01b4d00623e58b321d
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0xa5Be7E7c19510e6DCaFBd9C612094c5eF3F88052
— Txhash: 0x4815553fb35660c2bb0471bc65692d8b942069586f7989d96372776c95605889
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0x93383b77f5694Ef824e1779E5cFDc0A15D0894ef
— Txhash: 0x8b5ffe553fc6d14aace9a10f123a3d0930d70a695b2448e8c828030abbf49006
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0xf7F8cBFE832F139D3f8E7280798b308Ac5dAd291
— Txhash: 0x391813708ff3058dea6fa9fccc8f0a956b53b24f32bdcc7cb3b2a3013b052ab7
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0x2056Be2a9a2c7cd0D6cb328451c11526C52dB8D0
— Txhash: 0x1042cb2c6d07efe45fa61c1f5db04745d458c835d91fa8edc47a3db53b5696b7
Binance Withdrawals and Deposits:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 and 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
— Pictures are below this section
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 received funds from Binance 114 times:
— From 0x564286362092D8e7936f0549571a803B203aAceD
— Txhash: 0x14def97773eec4d7027247a7d9eadd7486b4cfb1568d7866f303b0da799f1698
— From 0x708396f17127c42383E3b9014072679b2F60B82f
— Txhash: 0xb59ebf7b4ed22b880ec5f6b7a1d06eb2f8666fadfa8490bc29620f5678dd5928
— From 0x4976A4A02f38326660D17bf34b431dC6e2eb2327
— Txhash: 0x785de0dba852b87b8eec62827f5b45927200fcd938e77f129f5b0dab86028722
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC received funds from Binance 11 times:
— From 0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE
— Txhash: 0x09a5931da97b9edd5da7cfc81cef8793930b879bab669e0ca7a49f6009a9834c
— From 0x0681d8Db095565FE8A346fA0277bFfdE9C0eDBBF
— Txhash: 0x7fe652e2b2a5a37bdcebf086916335ad5926b6a2a512c209df1ecf69f1d7d57e
— From 0x21a31Ee1afC51d94C2eFcCAa2092aD1028285549
— Txhash: 0x391da848bd47ab74e81e8d2043c7328dbe4107f11f1b861b34d1445536543a33
Binance Deposits:
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
To 0xaCFF2c2d1cDC0a74b3f5ec2A953977Ba7631B7Ca
— Txhash: 0x3bf605d2df43f9e9f0dbf10cbe2f9e8d494ea3e12910246d5f1c68752444830f
To 0x2Bc812C70dCd634A07Ce4fb9cD9bA4319Fd9898D
— Txhash: 0xfd43e47fa411ea3a1311ee899de1d44f1e0e3459ba0c0560a6415852ee9c822a
To 0x20E3A9CF9f2d4773dE24Fb50B1EfF25fed70aCC3
— Txhash: 0xbe16154b2d28f2f96d8b2e8da790396b46fc439d1c5085567b4dcf5ba065cb6a
Hitbtc Deposit Addresses:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0x69D2fB1D0B72BcD0A9C8793EB811e6d1D0A65454
— Txhash: 0x33e00a362728353db3d3b7d1d9ba014a39d90c9997ee792e15f5d52ed3c1e989
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0xe181a1F9a75591D33845108a5eFeD24b072e500C
— Txhash: 0x3613bd47190226845d12159ccca2e744ae1cf3298a2eca01b4d00623e58b321d
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 to 0xa5Be7E7c19510e6DCaFBd9C612094c5eF3F88052
— Txhash: 0x4815553fb35660c2bb0471bc65692d8b942069586f7989d96372776c95605889
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0x93383b77f5694Ef824e1779E5cFDc0A15D0894ef
— Txhash: 0x8b5ffe553fc6d14aace9a10f123a3d0930d70a695b2448e8c828030abbf49006
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0xf7F8cBFE832F139D3f8E7280798b308Ac5dAd291
— Txhash: 0x391813708ff3058dea6fa9fccc8f0a956b53b24f32bdcc7cb3b2a3013b052ab7
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0x2056Be2a9a2c7cd0D6cb328451c11526C52dB8D0
— Txhash: 0x1042cb2c6d07efe45fa61c1f5db04745d458c835d91fa8edc47a3db53b5696b7
Binance Withdrawals and Deposits:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 and 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
— Pictures are below this section
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 received funds from Binance 114 times:
— From 0x564286362092D8e7936f0549571a803B203aAceD
— Txhash: 0x14def97773eec4d7027247a7d9eadd7486b4cfb1568d7866f303b0da799f1698
— From 0x708396f17127c42383E3b9014072679b2F60B82f
— Txhash: 0xb59ebf7b4ed22b880ec5f6b7a1d06eb2f8666fadfa8490bc29620f5678dd5928
— From 0x4976A4A02f38326660D17bf34b431dC6e2eb2327
— Txhash: 0x785de0dba852b87b8eec62827f5b45927200fcd938e77f129f5b0dab86028722
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC received funds from Binance 11 times:
— From 0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE
— Txhash: 0x09a5931da97b9edd5da7cfc81cef8793930b879bab669e0ca7a49f6009a9834c
— From 0x0681d8Db095565FE8A346fA0277bFfdE9C0eDBBF
— Txhash: 0x7fe652e2b2a5a37bdcebf086916335ad5926b6a2a512c209df1ecf69f1d7d57e
— From 0x21a31Ee1afC51d94C2eFcCAa2092aD1028285549
— Txhash: 0x391da848bd47ab74e81e8d2043c7328dbe4107f11f1b861b34d1445536543a33
Binance Deposits:
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
— To 0xaCFF2c2d1cDC0a74b3f5ec2A953977Ba7631B7Ca
— Txhash: 0x3bf605d2df43f9e9f0dbf10cbe2f9e8d494ea3e12910246d5f1c68752444830f
— To 0x2Bc812C70dCd634A07Ce4fb9cD9bA4319Fd9898D
— Txhash: 0xfd43e47fa411ea3a1311ee899de1d44f1e0e3459ba0c0560a6415852ee9c822a
— To 0x20E3A9CF9f2d4773dE24Fb50B1EfF25fed70aCC3
— Txhash: 0xbe16154b2d28f2f96d8b2e8da790396b46fc439d1c5085567b4dcf5ba065cb6a
Coinbase Deposits and Withdrawals:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 and 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC
— *Pictures will be below*
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 withdrew from Coinbase 8 times:
— From 0x3cD751E6b0078Be393132286c442345e5DC49699
— Txhash: 0x4dfbaf7467663de9d61d95483419d166bf4bb64c887e67da13a35f40df44a965
— From 0x3cD751E6b0078Be393132286c442345e5DC49699
— Txhash: 0xc8c0928961ac642034eee1b2f889c298a1b40b55b2242471581cf6f36d88b49d
— From 0xA9D1e08C7793af67e9d92fe308d5697FB81d3E43
— Txhash: 0xa9704f7503da94aafb66cf7477a2d0085dffcee17dd6805b1f89b5ea390d0886
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6 sent funds to Coinbase deposit addresses:
— To 0x40347Ed656BD5a43599A1Bd60682F7088A60129f
— Txhash: 0x08309866cd4d9a5fb10606971a9bde3b07c54e13723013d6df6d70cf0c713c83
— To 0x026B97cC0403f23cc2fd5d3052471c5923A4F428
— Txhash: 0xe1162f7788142dec93402ea88505c029b89c6198e1621b55211e5a74e3577811
— To 0x683d1aD93883e7ffDCc06262B069FE2797112154
— Txhash: 0xbc6b1b0f62903d3c57cea12e9153bf1bef2b82af1eb152d2ebb5a9e3b6e655e1
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC withdrew from Coinbase 4 times:
— From 0xddfAbCdc4D8FfC6d5beaf154f18B778f892A0740
— Txhash: 0x402ec401ec3f110e7ef8ab1935c06d873d49bfb9cf99c83be43966db46e675b5
— From 0xddfAbCdc4D8FfC6d5beaf154f18B778f892A0740
— Txhash: 0x6ab938b65b54333daba8aefe93cec7e90c083e8e6e6fb782157f77179425623d
— From 0xb5d85CBf7cB3EE0D56b3bB207D5Fc4B82f43F511
— Txhash: 0x2f86042df74d285d35799efcc03488f517ae250d2b840e4c5ba58bcd44619b72
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC sent funds to Coinbase deposit addresses:
— To 0x0702f41d9E2673389925DE1793009EB1B674eca1
— Txhash: 0x69e5fbefd651a823d208108284cefca0fa34f6f1aef142c7f14635495d7b6c1b (Polygon chain)
— To 0x48544FF04b69661Fa82fB9A01a03cb6C50d44B9E
— Txhash: 0x0ffbfa1a2ed5242919c28605275a4bd2ce22f1fb508bc7902968269e65687832
— To 0x363E0a03b7B06762A0229a17C0A4aD5F63e0C9E3
— Txhash: 0x2891a8c61d436fec9ca1a186b72d240b39c825106b8089edad407d8cf330c94b
A few more addresses and important points to note, at the end of this paragraph there is a mapping tool that will help you better visualize everything you have read so far.
ChangenowThe Withdrawals and Deposits:
- 0x230C67a5970Dc736d63c889CaCde226d5F370AD6:
— Received funds from 0x8f54972F4Ca40bD3ffC8b085f6Ece1739C40c65f (Changenow exchange, labeled as fake phishing on Etherscan)
— Txhash: 0xbea2176a67502b03810be7f808b003e976a1a2aa79f5a1356ccd26b1f468e073
- 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC:
— Received funds from 0x2caB3DEfed9CC52827ecf37536A131C7da6CD5Aa (Changenow exchange, Polygon chain)
— Txhash: 0x07665a45e1be7475fa0375425638a60f2dd05849aab22be96efed2bf6aae57c5
— Sent funds to Changenow deposit addresses:
— 0x82B1b769211824817d24b3a565B5c5636FCAf89A
— Txhash: 0x7e1bdee2f64c88ec11adb743078e10d5c7d57e8ede4fccae444b5c2fff2e9fcd
— 0xceB33eCB9F3c34EEf29d3a0D28889b879b1Adc20
— Txhash: 0x89ed5570018851003756c59b1172e67ddd84c2d086ee0ca04d4cd6688f4855f1
— 0x99c4B9C408624C5aB8E66a72f34B6A74F49D8F90
— Txhash: 0x968bf4483c8636f16316464b7d0c61b4c99f47631832722df0580b9378c88525
Connections of 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to Possible Leads/Suspects:
- Interacted with 0x3fd3D51F0C35918C3a734cFDf8e10a439519C928 (Juniorone) via OpenSea profile 22 times, first funded 0x3fd.
— Txhash: 0x184a21a0fb11b6e78d683ef10239b0b330f588bf56716c5fe1fec60a5a109e52
- 0x3fd3D51F0C35918C3a734cFDf8e10a439519C928 is a fan of Unstoppable Domains, similar to 0x43Bf7BcF64C501D5f4632d7f1cCE6779aeA3c8b3 (klauss.x).
- Shared the same KuCoin deposit address (0xB4eE6433D07E3d7Eeb3709Dd75299aC8238Ab5da):
— 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC to 0xB4eE6433D07E3d7Eeb3709Dd75299aC8238Ab5da
— Txhash: 0xc8ea03e68ff490c5e42695ab57fd6f674a8c53c2863531711a22ca3e4cc20193
— 0x3fd3D51F0C35918C3a734cFDf8e10a439519C928 to 0xB4eE6433D07E3d7Eeb3709Dd75299aC8238Ab5da
— Txhash: 0xe5c55a1ec07ecceb891c8e470c51b640cf460bbeb7e78fa5ecec03cad4e69552
- 0x3fd3D51F0C35918C3a734cFDf8e10a439519C928 has interacted on different chains, notably the Flare blockchain with over 112 transactions.
- Interacted with 0x8290e4e246428c78C2bC4043E2C83a2136A11d54 21 times.
— Txhash: 0xaaf457050e2af93c26eaa80d263cb5e6255cc120739249a20b2acc1cc1dcd98e
- 0x8290e4e246428c78C2bC4043E2C83a2136A11d54 was first funded by 0xe3bDa3fADfCFD24159e9A28e4ef304Fa5EC0D8BC.
— Txhash: 0x86ee814a5c7e2cfe83c1d757a3afa66121c28388473b937123d096c6a0b986ca
- 0x8290e4e246428c78C2bC4043E2C83a2136A11d54 sent funds to 0x52bAa34672DedB061Ffd3EA8683a41E89F56A60b.
— Txhash: 0x3c51771a3a310d48d93ffe61e58d1c5d93cdb9b13b1497cf347914de2c6580ae
- 0x52bAa34672DedB061Ffd3EA8683a41E89F56A60b is a strange address, with almost every inflow transaction immediately going to a deposit address, except one to 0x670B2136cB68B85Be41b8a1c84DDfe11a356D534, which holds $5,330,465 in ETH.
— Txhash: 0x076fef091c7dab9fb2fc79dad914a6739e2d18b6d123c26a657054881bb6fff3
- Two wallets that sent funds to 0x52bAa34672DedB061Ffd3EA8683a41E89F56A60b:
— 0x12f0D6cA791ead064bB8BA1e0ce59523aeD2265a (ElGuero aka Bryan Alejandro)
— Txhash1: 0xe4c3958c4eaf82c50681444a6766437877a2695a0970f34203e951335cb69e42
— 0x486d51999f6baCcF2Ed6e3b627E1BEc1F55Aa6c5
— Txhash2: 0x92ce90b6df4fbc49cdd33472c40d64013c80f29516c20be6ee33ad491799c1db
We were able to make concrete links between addresses and social networking profiles.
- ElGuero’s Twitter: [ElGueroPalma33](https://twitter.com/ElGueroPalma33)
— Tweet showing wallet ownership: [Tweet](https://x.com/ElGueroPalma33/status/1502956204598853633)
— TikTok: [ElGueroPalma33](https://www.tiktok.com/@ElGueroPalma33?lang=en)
— Instagram: [MrB49ersfaithful](https://www.instagram.com/mrb49ersfaithful/)
- 0x486d51999f6baCcF2Ed6e3b627E1BEc1F55Aa6c5 was first funded by 0x95D75D9af44956Dd08616D4E814141f5AcFCa632.
— Txhash: 0xe4ee4462525acb641a8de1f84dd85e9007538584cccbe49b17451e3b522ddcf7
- 0x95D75D9af44956Dd08616D4E814141f5AcFCa632 interacted with 0xd98C62896bC49734612b3880ae0ebdA7C9961280 (beastyROGUE) 12 times.
— Txhash: 0xc5df3527b286dc3f2bae2e83a76a2e546d8693335ec9f5a634ec98468a09f27b
- BeastyRogue’s Twitter: [beastyROGUE](https://twitter.com/beastyROGUE)
— Tweet about buying tokens on Uphold and Bitrue: [Tweet](https://x.com/beastyROGUE/status/1613972086984146977)
- Possible related Instagram: [iammontroseco](https://www.instagram.com/iammontroseco/)
Metasleuth Mapping
Thanks to visual mapping you’ll get better compression, here’s the color key
— White: Hitbtc71C deposit address, hacker, and connected wallets
— Blue: Deposit addresses
— Green: Exchange addresses
— Purple: Potential suspects/leads
— Yellow: Dev other compromised wallets
— Brown: Wallets that deposited/sent funds to Hitbtc71C deposit address
— Orange: Strong intermediary direct connections regarding two wallets mentioned in the report
— Red: Hacker wallet that transferred funds from other dev compromised wallets, where current funds are held
metasleuth.io link is here
Pictures below are from this part of the report and onward, in order.
Conclusion
The individual known as “Anan Phoon” was found to be a fake identity, with the real perpetrator linked to the DPRK/Lazarus hacker group. This person used multiple aliases and accounts across various platforms to carry out the attack and mislead the community.
This report was written in close collaboration with Lukas, ChainResidue, a part of the valuable community members, and the team, this is the result of months of research.
In conclusion, while the $GB token incident was a significant setback, it has provided valuable lessons and insights. By sharing our findings, we hope to contribute to a more secure and resilient Web3 ecosystem.
________________________________________________________________
I would like to express my deep gratitude to the Reflect community for its unwavering support and resilience during this difficult period. Your unwavering commitment and solidarity have been a strength in helping me navigate through the complexities of the $GB token incident. Despite the adversity, your confidence and patience helped me work towards a more secure future. Thank you for supporting me.
From Yusei, for better days.







