Bitget — ETH address 0xC48af6…Dd5c1f

0xC48af6eB436A41914D82a45BF196aee25bDd5c1f

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 1 hop from documented incident (0x8c701b…d377b3).

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 1 hop from documented incident (0x8c701b…d377b3).0x8c701bcc2d3001bb22f474b8a182f58ef8d377b3documented incident1inbound
Funds reaching this address are 3 hops from documented incident (0x770b10…8463ee).0x770b10b273fc44fe9197d6bf20f145c2e98463eedocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x52f08f…25d284).0x52f08feb1b0da609a5442514e2bb43c99d25d284documented incident3inbound
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 5 hops from documented incident (0x469ac1…7425dc).0x469ac1406de92f82c0563477240a3627057425dcdocumented incident5inbound
Funds reaching this address are 5 hops from documented incident (0x94a43d…135da0).0x94a43df7687a8494948be937400e9d5d33135da0documented incident5inbound
Funds reaching this address are 5 hops from documented incident (0xe410a2…f0d946).0xe410a2e5710ee787bcaa63f52a3943ff71f0d946documented incident5inbound
Funds reaching this address are 5 hops from documented incident (0x7c9627…573e1c).0x7c96279ec1e888aa56b9b836e0db26ca48573e1cdocumented incident5inbound
Funds reaching this address are 5 hops from documented incident (0x030f43…597050).0x030f43ce321210f5eb25c8601528cf4cb5597050documented 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.