Bitget — ETH address 0x989111…B98a1f

0x989111C544eCC47Ede54A1191dAb46ac8dB98a1f

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 (0x989111…b98a1f).

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 (0x989111…b98a1f).0x989111c544ecc47ede54a1191dab46ac8db98a1fdocumented incident0inbound
Funds reaching this address are 1 hop from documented incident (0x030f43…597050).0x030f43ce321210f5eb25c8601528cf4cb5597050documented incident1inbound
Funds reaching this address are 2 hops from documented incident (0x10532e…b8b057).0x10532ecc22300da32c9c586c1187a25876b8b057documented incident2inbound
Funds reaching this address are 8 hops from OFAC SDN list (0x098b71…3e2f96).0x098b716b8aaf21512996dc57eb0615e2383e2f96OFAC SDN list8inbound
Funds reaching this address are 8 hops from sanctioned entity (entity attribution) (0x475664…a704f2).0x475664cdedb4ffaf34a81c2a83e2c09417a704f2sanctioned entity (entity attribution)8inbound
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
Funds reaching this address are 5 hops from documented incident (0x00f51c…6a6cd3).0x00f51c341ccafa94cc56a037338d9b60d96a6cd3documented incident5inbound
Funds reaching this address are 5 hops from documented incident (0x43848a…2a979c).0x43848aa5a092a9f4382c3e6eacc0bc47fe2a979cdocumented incident5inbound

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.