ETH address 0x2d461c…4B7164

0x2d461c0Fae50aBF852AC59BC0709411BB34B7164

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 size143,289 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 (0x2d461c…4b7164).0x2d461c0fae50abf852ac59bc0709411bb34b7164documented incident0inbound
Funds reaching this address are 9 hops from OFAC SDN list (0x1999ef…0c5ade).0x1999ef52700c34de7ec2b68a28aafb37db0c5adeOFAC SDN list9inbound
Funds reaching this address are 9 hops from OFAC SDN list (0x5a14e7…f58f51).0x5a14e72060c11313e38738009254a90968f58f51OFAC SDN list9inbound
Funds reaching this address are 3 hops from documented incident (0xda3f8d…ebf63c).0xda3f8db5f3ecb711a5c6952f0b14eb0005ebf63cdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xe90a3c…6689d5).0xe90a3c163abcb8296080f06b9a9122499d6689d5documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xdb2505…ba20a1).0xdb25055ca6e20cdd6e672a4cc93b87a736ba20a1documented incident3inbound
Funds reaching this address are 4 hops from documented incident (0xfd6fce…c98bdb).0xfd6fce575e3a117a0d889d1b32b5e3d5e5c98bdbdocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xfc1063…fa85a5).0xfc1063cb3885da495ae63c58e35d60100dfa85a5documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x8f9a8d…07c879).0x8f9a8dc65a423c7dec9261aa6010db738407c879documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x919c57…d29bd4).0x919c570a707c322dcecb43f474b1aeff9bd29bd4documented 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.