Bitget — ETH address 0xbf3071…3ac7d0

0xbf3071A89a61C4CAb078100A3Ea2D8d2503ac7d0

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 (0xbf3071…3ac7d0).

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 (0xbf3071…3ac7d0).0xbf3071a89a61c4cab078100a3ea2d8d2503ac7d0documented incident0inbound
Funds reaching this address are 1 hop from documented incident (0x030f43…597050).0x030f43ce321210f5eb25c8601528cf4cb5597050documented incident1inbound
Funds reaching this address are 1 hop from documented incident (0xe58b5b…5f2420).0xe58b5b0b434fdaa0e9f7b7e98a6f402e545f2420documented incident1inbound
Funds reaching this address are 2 hops from documented incident (0x10532e…b8b057).0x10532ecc22300da32c9c586c1187a25876b8b057documented incident2inbound
Funds reaching this address are 2 hops from documented incident (0x989111…b98a1f).0x989111c544ecc47ede54a1191dab46ac8db98a1fdocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xb48888…b1a17f).0xb488886d0bc487e4d1547a5281722ab257b1a17fdocumented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xb81f2e…c6a7a1).0xb81f2e952d954ae914591db4d9e421eb7fc6a7a1documented incident2inbound
Funds reaching this address are 4 hops from documented incident (0x543286…4eb113).0x54328634060788df7d98b3b3b1e347235c4eb113documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x5b500d…3f5735).0x5b500d11c53dd0bdc792b5c55c4ff550e83f5735documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xf7bc92…b396c3).0xf7bc92103f23ef312658cd9b81dc2713f7b396c3documented 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.

0xbf3071…3ac7d0 (Bitget) ETH address check | PublicAML