Bitget — ETH address 0xbed053…4c9f78

0xbed053C002aEc6fb6f3F7a5bd73C921CcA4c9f78

PublicAML knows this Ethereum address as Bitget, 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 (0xbed053…4c9f78).

What we know about this address

ChainEthereum (ETH)
EntityBitget
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 (0xbed053…4c9f78).0xbed053c002aec6fb6f3f7a5bd73c921cca4c9f78documented incident0inbound
Funds reaching this address are 1 hop from documented incident (0xe241b5…cfb60f).0xe241b53392b5c57a66290c62c14547439dcfb60fdocumented incident1inbound
Funds reaching this address are 1 hop from documented incident (0x0fc8da…9411b0).0x0fc8dac9c3d857acc3d53b8a1c0b5b2cb29411b0documented incident1inbound
Funds reaching this address are 2 hops from documented incident (0x405118…1af8eb).0x405118d5a9b2776fa9dfacd9c4f18701451af8ebdocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0x2fb385…de7894).0x2fb385dd06a8212c5c13cbf0efedcb3d1cde7894documented incident2inbound
Funds reaching this address are 3 hops from documented incident (0x865d56…ea6715).0x865d5600118703043d03b5285969fd5077ea6715documented incident3inbound
Funds reaching this address are 4 hops from documented incident (0xabb8f9…ccbda7).0xabb8f9e2951bddbbbbcd4f59b02320b833ccbda7documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x5648b9…caf70c).0x5648b985f91616470edf7bba8775a3a5f7caf70cdocumented incident4inbound
Funds reaching this address are 6 hops from documented incident (0x5be003…3acf7b).0x5be00368262992f260a6b2b4f9837c4bcc3acf7bdocumented incident6inbound
Funds reaching this address are 6 hops from documented incident (0x770b10…8463ee).0x770b10b273fc44fe9197d6bf20f145c2e98463eedocumented incident6inbound

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.