ETH address 0x9457C3…23243e

0x9457C385D12C800E3695376eFAE905265423243e

PublicAML knows this Ethereum address as a phishing address. Our AML risk score for it is 100 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 score100 / 100 (critical)
Cluster size2,323,073 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 (0x9457c3…23243e).0x9457c385d12c800e3695376efae905265423243edocumented incident0inbound
Funds reaching this address are 1 hop from documented incident (0xfc1063…fa85a5).0xfc1063cb3885da495ae63c58e35d60100dfa85a5documented incident1inbound
Funds reaching this address are 1 hop from documented incident (0xf26c5f…7a1a13).0xf26c5f062f3638ab7e880f6e9efc49c2157a1a13documented incident1inbound
Funds reaching this address are 7 hops from OFAC SDN list (0xdcbeff…643193).0xdcbeffbecce100cce9e4b153c4e15cb885643193OFAC SDN list7inbound
Funds reaching this address are 8 hops from OFAC SDN list (0x4f47bc…96270c).0x4f47bc496083c727c5fbe3ce9cdf2b0f6496270cOFAC SDN list8inbound
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 7 hops from documented incident (0xac834b…c04f67).0xac834bf30aea9739371331c93384c21951c04f67documented incident7inbound
Funds reaching this address are 7 hops from documented incident (0x772ac4…741cf2).0x772ac4aecfba051ed256715f61821ac85c741cf2documented incident7inbound
Funds reaching this address are 3 hops from documented incident (0xc8edb9…4b6e67).0xc8edb98eb5002d7d8b0f9aa7ccb9c487084b6e67documented incident3inbound

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.