Bitget — ETH address 0x405118…1Af8EB

0x405118d5A9b2776fa9DFacD9C4F18701451Af8EB

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 (0x405118…1af8eb).

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 (0x405118…1af8eb).0x405118d5a9b2776fa9dfacd9c4f18701451af8ebdocumented incident0inbound
Funds reaching this address are 1 hop from documented incident (0x3caaa2…17f56e).0x3caaa2cbae7f21e2b9f187724b5010a27c17f56edocumented incident1inbound
Funds reaching this address are 2 hops from documented incident (0xabb8f9…ccbda7).0xabb8f9e2951bddbbbbcd4f59b02320b833ccbda7documented incident2inbound
Funds reaching this address are 12 hops from OFAC SDN list (0x098b71…3e2f96).0x098b716b8aaf21512996dc57eb0615e2383e2f96OFAC SDN list12inbound
Funds reaching this address are 13 hops from EU sanctions list (0x002471…f56f8d).0x002471b8a185f9980708d0eaec5b289714f56f8dEU sanctions list13inbound
Funds reaching this address are 14 hops from OFAC SDN list (0x7ced75…27361e).0x7ced75026204ac29c34bea98905d4c949f27361eOFAC SDN list14inbound
Funds reaching this address are 14 hops from OFAC SDN list (0xf4377e…d602d4).0xf4377eda661e04b6dda78969796ed31658d602d4OFAC SDN list14inbound
Funds reaching this address are 14 hops from OFAC SDN list (0x57ec89…761259).0x57ec89a0c056163a0314e413320f9b3abe761259OFAC SDN list14inbound
Funds reaching this address are 4 hops from documented incident (0x5be003…3acf7b).0x5be00368262992f260a6b2b4f9837c4bcc3acf7bdocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xdd6612…ccc828).0xdd6612a6d64d66fab5a8a5ba69fe3a7e7bccc828documented 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.