ETH address 0x7848aA…dd0231

0x7848aA63E9BeEc2405Dc3e5e58eDb568a8dd0231

PublicAML knows this Ethereum address as a phishing address. Our AML risk score for it is 90 of 100, which we read as critical risk. This address is itself listed by documented incident.

What we know about this address

ChainEthereum (ETH)
Categoryphishing
AML score90 / 100 (critical)
Cluster size276,998 addresses

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.documented incident0direct
This address is itself listed by documented incident (0x7848aa…dd0231).0x7848aa63e9beec2405dc3e5e58edb568a8dd0231documented incident0inbound
Funds reaching this address are 5 hops from documented incident (0xe52197…0a5138).0xe52197218e5208160df55eff1ed1e3e9210a5138documented incident5inbound
Funds reaching this address are 6 hops from documented incident (0xb73005…a25213).0xb7300518548351b8c6911405f148a241d9a25213documented incident6inbound
Funds reaching this address are 4 hops from documented incident (0xfae752…abd9e3).0xfae752581b9fd547c1652d7a417efced94abd9e3documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x8e10f0…5d7873).0x8e10f088e0a046b2467f89114520381f2b5d7873documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x9653d4…b4a86c).0x9653d4d2c71cf7f61ba53b92355874e07bb4a86cdocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x962b55…34a029).0x962b55decacd69b74d83a1738b1e42c1e834a029documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x967582…13b80a).0x967582debedf069111973313e29bc7c5f713b80adocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x919c57…d29bd4).0x919c570a707c322dcecb43f474b1aeff9bd29bd4documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x952782…7b3c82).0x9527821d55f9e458d22b9f18f0d2eebb407b3c82documented 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.