Wallet Private Key Leak Due to Hacker Attack

Token Design
1

Dear Team,

A wallet hacking incident occurred today. Here’s the relevant Twitter post: @adspowercn. This company specializes in fingerprint browsers designed to isolate IPs and facilitate interactions across multiple wallets.

The stolen funds were transferred to the following address: 0xf772Be79Bd6D1F4316e938C6c40cF68CF6911c81. Currently, a total of 19,600 wallet private keys have been leaked, most of which belong to wallets mass-produced by studios.

I suggest either:

  1. Adding these wallets to the Sybil list to prevent misuse.
  2. Implementing a feature allowing wallet owners to voluntarily opt-out of receiving airdrops, which could help prevent tokens from falling into the hands of hackers.
5 Likes
2

Those hacked wallets needs to be removed from airdrop lists.

Key is stolen which means that there is no way to prove who is the real owner of hacked wallets.

1 Like
3

I just found out the function of browser. It is pretty must suspicious that only sybils are using that browser for multi–account farming. Regardless of they are sybil or not, they must be excluded because wallets are already hacked and there is no single reason to assign token to hacked wallet.

4

@dfox Can you please share your thought?