Upbit hack — ETH address 0x44d163…6eE159

0x44d163e10058573d2Df684635d96f61FB56eE159

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)
Cluster size635,316 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.

FindingSourceHopsDirection
This address is itself listed by documented incident.documented incident0direct
This address is itself listed by documented incident (0x44d163…6ee159).0x44d163e10058573d2df684635d96f61fb56ee159documented incident0inbound
Funds reaching this address are 1 hop from documented incident (0xa72e91…562ef1).0xa72e917a995d8145f181cf1c37cdeb4e47562ef1documented incident1inbound
Funds reaching this address are 3 hops from documented incident (0x07be28…f71665).0x07be287f8756092fd4f58b7d967d356d89f71665documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x0e40fd…e4d915).0x0e40fd74122a23b960af3dd84084500e83e4d915documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x15922c…13df37).0x15922c70132210b3ed785e2c028aaf456513df37documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x17a48e…afa8ea).0x17a48e2ab13b778984e85733e3f78d5cffafa8eadocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x192ffd…7e3d03).0x192ffd2a3a09bfe70248109089d2a586987e3d03documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x2aee20…58554b).0x2aee204507c3a00ee2df22da3f1b762e9558554bdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xf0b5ef…52db5e).0xf0b5efe097f5520ec59bc473e3c5e9e9e652db5edocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xf95e75…f85f62).0xf95e75dbdf381acc99eb40d27f551b3c2df85f62documented incident3inbound

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.