ETH address 0x3376B0…8BE9f4

0x3376B087316F3697242A0b782fdf38Cd088BE9f4

PublicAML knows this Ethereum address as a phishing address. Our AML risk score for it is 97 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 score97 / 100 (critical)
Cluster size41,426 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 (0x3376b0…8be9f4).0x3376b087316f3697242a0b782fdf38cd088be9f4documented incident0inbound
Funds reaching this address are 4 hops from documented incident (0xe29a07…2994dd).0xe29a07002c7be4299b51a2892799cc4a372994dddocumented incident4inbound
Funds reaching this address are 5 hops from documented incident (0xba5ed1…a22ebe).0xba5ed1488be60ba2facc6b66c6d6f0befba22ebedocumented incident5inbound
Funds reaching this address are 4 hops from documented incident (0xfd6fce…c98bdb).0xfd6fce575e3a117a0d889d1b32b5e3d5e5c98bdbdocumented 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 (0x915184…addd9c).0x91518450bd1cb56ac96d7855fb1081a8bfaddd9cdocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x926ee8…144db0).0x926ee893b7a9d9edce57cbb7195f4aa431144db0documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x95a4ee…58345d).0x95a4ee08cd409ca66395fd10ad19cef80258345ddocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xc8edb9…4b6e67).0xc8edb98eb5002d7d8b0f9aa7ccb9c487084b6e67documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0xce322d…29bb2b).0xce322d2506cd7ced3f1754d1ffb483225e29bb2bdocumented 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.