Bitget — ETH address 0x3a9b20…2EE7db

0x3a9b20E81355403cFF18c227EDa590E4bC2EE7db

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. Funds reaching this address are 2 hops from documented incident (0x5648b9…caf70c).

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
Funds reaching this address are 2 hops from documented incident (0x5648b9…caf70c).0x5648b985f91616470edf7bba8775a3a5f7caf70cdocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xf5cb70…62842e).0xf5cb7088c6b5c7dd57711ec1a5c978137f62842edocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0x6d329c…93cc16).0x6d329c9db8e8b716e4bec0285706ec714493cc16documented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xbc7c0f…73757e).0xbc7c0f10eb697dbe156b0b62ef77a9bd2573757edocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xd91542…00b424).0xd9154200c6a4ec3bab1e4a36a98a9346d800b424documented incident2inbound
Funds reaching this address are 3 hops from documented incident (0x3302cd…a93201).0x3302cd93a0e22f3bfa7b46b48c27d5428ba93201documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x496974…04ac34).0x4969741f4e33172a3eea54f8ea2df3779a04ac34documented incident3inbound
Funds reaching this address are 4 hops from documented incident (0x770b10…8463ee).0x770b10b273fc44fe9197d6bf20f145c2e98463eedocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x52f08f…25d284).0x52f08feb1b0da609a5442514e2bb43c99d25d284documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xdc2901…91dc63).0xdc2901f741b4003e32b8b752e97b8c4c1891dc63documented 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.