PublicAML

Phishing address flagged by Etherscan (Fake_Phishing4848937) — ETH address 0x0BD77C…0e6A77

0x0BD77C7c70d342222C05d407eAc45CB5AE0e6A77

PublicAML knows this Ethereum address as Phishing address flagged by Etherscan (Fake_Phishing4848937), 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 flagged by Etherscan (Fake_Phishing4848937)
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 (0x0bd77c…0e6a77).0x0bd77c7c70d342222c05d407eac45cb5ae0e6a77documented incident0inbound
Funds reaching this address are 5 hops from OFAC SDN list (0xed6e0a…bad921).0xed6e0a7e4ac94d976eebfb82ccf777a3c6bad921OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x4f47bc…96270c).0x4f47bc496083c727c5fbe3ce9cdf2b0f6496270cOFAC SDN list5inbound
Funds reaching this address are 6 hops from OFAC SDN list (0x12ea80…6f4e8d).0x12ea80238c7d805d003ce793594e92d84a6f4e8dOFAC SDN list6inbound
Funds reaching this address are 4 hops from documented incident (0xdcc8a3…952c28).0xdcc8a38a3a1f4ef4d0b4984dcbb31627d0952c28documented incident4inbound
Funds reaching this address are 5 hops from documented incident (0x629e7d…96b71a).0x629e7da20197a5429d30da36e77d06cdf796b71adocumented incident5inbound
Funds reaching this address are 6 hops from documented incident (0x7d522f…b9d082).0x7d522f67268f1c46d888fe083aaa86f784b9d082documented incident6inbound
Funds reaching this address are 6 hops from documented incident (0xa57eda…cf8956).0xa57eda20be51ae07df3c8b92494c974a92cf8956documented incident6inbound
Funds reaching this address are 6 hops from documented incident (0x680910…55f36b).0x680910cf5fc9969a25fd57e7896a14ff1e55f36bdocumented incident6inbound

1 further internal signal is 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.

  • Named as a perpetrator in Phishing address flagged by Etherscan (Fake_Phishing4848937). Source: etherscan.io

More addresses in this index

These are other addresses in the PublicAML index, 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.