Aimtron — alleged breach
One linked filing — more sources may join as they report · filed May 26, 2023. View entity profile → Other incidents for this victim →
incident inc_800e873cd83d40fe · merged by deterministic
Unverified threat-actor claim — not a regulatory filing
Attribution, victim identity, and counts shown here derive from LockBit 3.x's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
The group LockBit 3.x listed Aimtron on its leak site on May 26, 2023 and says the data has been published. No regulatory filing corroborates this claim yet.
Litigation Timing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.
Member cascade — every filing about this breach
- MAY 26Leak sitelockbit_3 postonly record · attacker claim · unverifiedday 0
- Watching: SEC 8-K · state-AG notices · victim statement. Median claim → filing gap is 64 days (day 1210 of watch).
Roll-up facts
- Breach window
- —
- Discovered
- —
- Affected
- —
- Data types
- —
- Threat actor
- LockBit 3.x (self-attributed)
Empty by design — an unverified claim can't establish these.
If this claim is true — what to expect
- ~64dMedian claim → filing gap for leak-site claims corpus-wide that DID corroborate — how fast confirmation arrives when it arrives, not how likely it is. A filing merges here automatically and upgrades this page.
- 5%Share of leak-site claims corpus-wide later corroborated by a regulatory filing (10,321 tracked, 365-day window). Most claims are never corroborated — this page stays an unverified claim until one is.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
No regulator filing linked yet.
No SEC filing or victim statement yet.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.