Live investigationBinance Hot Wallet Exploit

This address is linked to the attacker.

Binance hot wallet hack — ETH address 0x62b16E…FfC82e

0x62b16E7Eb76BE5Adbe544659cf246fF870FfC82e

PublicAML knows this Ethereum address as Binance hot wallet hack, a hack. Our AML risk score for it is 100 of 100, which we read as critical risk. Funds reaching this address are 1 hop from reader report to PublicAML (0x119209…2d7a16).

What we know about this address

ChainEthereum (ETH)
EntityBinance hot wallet hack
Categoryhack
AML score100 / 100 (critical)
Issuer freezeassets frozen by the token issuer

Risk findings

Each row carries the source that flagged it. A row at zero hops names this address directly; any other row is a path our propagation engine traced from a flagged address to this one. A finding is an observation about the flow of funds or about a published listing, not a statement about the owner of this address.

FindingSourceHopsDirection
Funds reaching this address are 1 hop from reader report to PublicAML (0x119209…2d7a16).0x1192093ad796156e29025af779542d6de62d7a16reader report to PublicAML1inbound
Funds reaching this address are 2 hops from reader report to PublicAML (0x56c3b3…332714).0x56c3b3224973dc7240877e630f37a160a5332714reader report to PublicAML2inbound
Funds reaching this address are 3 hops from reader report to PublicAML (0x137237…eac7c1).0x13723799ec02d2ab3933be11c7eb7c9904eac7c1reader report to PublicAML3inbound
Funds reaching this address are 4 hops from reader report to PublicAML (0x4bd7a5…52b29f).0x4bd7a51d216e7d406811b11ffc8e1caad452b29freader report to PublicAML4inbound
Funds reaching this address are 5 hops from reader report to PublicAML (0x6abec1…88cc3f).0x6abec14ec8dba805c3bc2e9133214a3c7688cc3freader report to PublicAML5inbound

2 further internal signals are held back from this page. They come from heuristics with known false positives, and we do not publish an accusation we would not defend. They are visible in the live check.

Incidents that name this address

Each line states the role this address plays in the incident as recorded. Being named as a victim, or as the recipient of funds, is not an accusation.

If this page is wrong

Attribution and risk propagation both make mistakes, and a page like this one is visible for a long time. If you own this address or can show that a finding here is incorrect, tell us and we will re-check it. Corrections are applied to the underlying data, so they carry over to the API and to every other view of this address.

Contact us about this address

See something wrong on this page? Tell us and we will check it.

PublicAML reports what it can observe on-chain and what public and vendor sources say about an address. Nothing on this page is a legal finding, an allegation against a person, or advice. Risk scores describe exposure through transaction paths, and an address can carry exposure without its owner having done anything wrong.

Data is read live from the PublicAML API at the time this page was served.

Is this your address?

Leave your email and we will watch this address for you: you hear from us when money moves through it or when what we know about it changes. We cannot recover anyone’s money, and we will not pretend otherwise — but you will not have to keep checking.

We use the address only to reach you about this wallet. No password to choose: you sign in with a code we email you.

If you want to put the whole account on record — what happened, when, how much — file a report. We never publish who filed one.

0x62b16E…FfC82e (Binance hot wallet hack) ETH address check | PublicAML