PublicAML

Limit Break — ETH address 0xddddD0…d52c24

0xddddD01e33c4dcF91bb0BDdDa40788dFAcd52c24

PublicAML knows this Ethereum address as Limit Break, a hack. 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)
EntityLimit Break
Categoryhack
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 (0xddddd0…d52c24).0xddddd01e33c4dcf91bb0bddda40788dfacd52c24documented incident0inbound
Funds reaching this address are 1 hop from documented incident (0xcccc64…eb3447).0xcccc640018f8c2b00fa45f456017ad2378eb3447documented incident1inbound
Funds reaching this address are 4 hops from documented incident (0x573790…72eace).0x57379063ee6e7b896182f0631427e1ce6472eacedocumented 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 (0xc81548…860c3a).0xc81548a3c601e2c41f9b4b38120860d8b0860c3adocumented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x3dd59d…a5f6b6).0x3dd59de66e2ad31a7d663df977ddd6e5f2a5f6b6documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x12591f…8b4991).0x12591f8e0b746761a75a5f9d52f5208a638b4991documented incident4inbound
Funds reaching this address are 4 hops from documented incident (0x2bca41…affc83).0x2bca419e570b1620b5e922fc005e806453affc83documented 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 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.