Phishing address (Etherscan public label) — ETH address 0xEb8f42…06060D

0xEb8f42582cfa46563FaC9d8798E3b15E1c06060D

PublicAML knows this Ethereum address as Phishing address (Etherscan public label), a phishing. 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)
EntityPhishing address (Etherscan public label)
Categoryphishing
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.documented incident0direct
This address is itself listed by documented incident (0xeb8f42…06060d).0xeb8f42582cfa46563fac9d8798e3b15e1c06060ddocumented incident0inbound
Funds reaching this address are 3 hops from attributed to a hacking entity (entity attribution) (0xd4004f…526bec).0xd4004f07d7b746103f2d9b4e5b5a540864526becattributed to a hacking entity (entity attribution)3inbound
Funds reaching this address are 3 hops from documented incident (0x30f220…336d01).0x30f22013cb880ea03402a4d71880024837336d01documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xaaf710…3f8cdc).0xaaf710a008c60ca60454fda7384a5b11313f8cdcdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xb39587…da6f50).0xb3958757fd6d2dfbcc934f39faa1f82210da6f50documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xda3f8d…ebf63c).0xda3f8db5f3ecb711a5c6952f0b14eb0005ebf63cdocumented incident3inbound
Funds reaching this address are 4 hops from documented incident (0x5c5b36…0aa9ce).0x5c5b3646368ff03f14f58b5e622b3f47f60aa9cedocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xfd6fce…c98bdb).0xfd6fce575e3a117a0d889d1b32b5e3d5e5c98bdbdocumented incident4inbound

2 further internal signals are held back from this page. They come from heuristics with known false positives, and we do not publish an accusation we would not defend. They are visible in the live check.

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.