Upbit hack — ETH address 0x52c2e3…Dd33Ce

0x52c2e3A608F7e6f32A829B017788c24309Dd33Ce

PublicAML knows this Ethereum address as Upbit hack, a hack. Our AML risk score for it is 100 of 100, which we read as critical risk. This address is itself listed by documented incident.

What we know about this address

ChainEthereum (ETH)
EntityUpbit hack
Categoryhack
AML score100 / 100 (critical)

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
This address is itself listed by documented incident.documented incident0direct
This address is itself listed by documented incident (0x52c2e3…dd33ce).0x52c2e3a608f7e6f32a829b017788c24309dd33cedocumented incident0inbound
Funds reaching this address are 1 hop from documented incident (0x2a10f9…af59dc).0x2a10f9c80e4f0f0f46fad80460ccde3ed4af59dcdocumented incident1inbound
Funds reaching this address are 1 hop from documented incident (0xfeefc9…144f55).0xfeefc9b1c8bcde0a900bfb9c1486e4a740144f55documented incident1inbound
Funds reaching this address are 1 hop from documented incident (0xd7a1c1…d6c2e2).0xd7a1c15fcb970dd45d1af03ff2e7c6147dd6c2e2documented incident1inbound
Funds reaching this address are 2 hops from documented incident (0x7b2797…c4300d).0x7b279751acb6cd91553c1580d95928588fc4300ddocumented incident2inbound
Funds reaching this address are 3 hops from documented incident (0xf46781…fefe3f).0xf4678169b1eb0c141fd99942ac02191145fefe3fdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x7400a2…36e715).0x7400a255a7521f4007e7c6dfbdd135f0b136e715documented incident3inbound
Funds reaching this address are 4 hops from documented incident (0x0651cc…2921c6).0x0651ccbcf0dadcea7b6696024c94a235eb2921c6documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x1195a3…3d9682).0x1195a388ad15e792b0c8d1c4d0c81827cb3d9682documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x30eec0…25017c).0x30eec09f344dce617ff04acf78355b9eef25017cdocumented incident4inbound

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.

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.

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.