Bitget — ETH address 0x69d85b…Ec27a5

0x69d85bb860e5Fd43873119cDeB8B99B49dEc27a5

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 (0x69d85b…ec27a5).

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 (0x69d85b…ec27a5).0x69d85bb860e5fd43873119cdeb8b99b49dec27a5documented incident0inbound
Funds reaching this address are 1 hop from documented incident (0x51190b…e84e6c).0x51190be1bac64a48f28043598f4c16c564e84e6cdocumented incident1inbound
Funds reaching this address are 2 hops from documented incident (0x99f531…bb3f5c).0x99f531bb6b7eadb76c0429a7bf47445e5ebb3f5cdocumented incident2inbound
Funds reaching this address are 3 hops from documented incident (0x08dc03…5d50e8).0x08dc03cab2b2f04d31cc45ca457ab476cb5d50e8documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x20f3af…452c8a).0x20f3afe8feb485790194e608d88b60b050452c8adocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x401bae…38db85).0x401bae4ef3eebdf34e75b6cf3755ba69b238db85documented incident3inbound
Funds reaching this address are 4 hops from documented incident (0xcfe25e…a8adcc).0xcfe25e689d37254c392ad683e9fcf9b9faa8adccdocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xe93d02…64a886).0xe93d025fa7441b8978fbd3099faa71bb0564a886documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xee45a8…5ce4af).0xee45a8d27b62e201a94d762915bd15686e5ce4afdocumented 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.