BC.Game Hacker — ETH address 0xA5e4F8…8580cA
0xA5e4F8141Cb2759CeA58F28cF2d0AB21b98580cA
PublicAML knows this Ethereum address as BC.Game Hacker, a hacker. Our AML risk score for it is 94 of 100, which we read as critical risk. This address is itself listed by attributed to a hacking entity (entity attribution).
What we know about this address
| Chain | Ethereum (ETH) |
| Entity | BC.Game Hacker |
| Category | hacker |
| AML score | 94 / 100 (critical) |
| Cluster size | 52 addresses |
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.
| Finding | Source | Hops | Direction |
|---|---|---|---|
| This address is itself listed by attributed to a hacking entity (entity attribution). | attributed to a hacking entity (entity attribution) | 0 | direct |
| This address is itself listed by attributed to a hacking entity (entity attribution) (0xa5e4f8…8580ca).0xa5e4f8141cb2759cea58f28cf2d0ab21b98580ca | attributed to a hacking entity (entity attribution) | 0 | inbound |
| Funds reaching this address are 2 hops from documented incident (0x4b0e8b…419e04).0x4b0e8b2c38b0044405e24db481d00be7d5419e04 | documented incident | 2 | inbound |
| Funds reaching this address are 5 hops from documented incident (0xb55cbb…6a4193).0xb55cbbb58f8c040bd3a06c065d99f9fd5d6a4193 | documented incident | 5 | inbound |
| Funds reaching this address are 6 hops from documented incident (0x4a7776…aed330).0x4a777646417b0fd34715d2b21d4a132c06aed330 | documented incident | 6 | inbound |
| Funds reaching this address are 6 hops from documented incident (0xa059aa…7f3c37).0xa059aaab82773caf622de9d9a0f2dbf9aa7f3c37 | documented incident | 6 | inbound |
| Funds reaching this address are 4 hops from documented incident (0x6849bb…a1df73).0x6849bbeae2f064ac56c9de588cfdc13f8ba1df73 | documented incident | 4 | inbound |
| Funds reaching this address are 4 hops from documented incident (0xdcc18f…40cd8e).0xdcc18f71318bdfb462274ea7561c82a3f540cd8e | documented incident | 4 | inbound |
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.
More addresses in this index
These are other addresses in the PublicAML directory, not counterparties of this one. Nothing here implies a connection between them.
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.
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.