LAVELLE INDUSTRIES, INC.
bd_6f0d81b6fa093116 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
For over 100 years, Lavelle has taken a leading role as a United States rubber and plastics manufacturer.665 Mchenry St Burlington, Wisconsin 53105, United StatesEmployees: 201 - 500revenue: $500M Kathryn TurkeVice President, Sales (OEM...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 28, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Indiana State AGbd_28965c2e6fb1f2092024-08-22 · +147dVerified
- Massachusetts State AGbd_37f30d65e1fc83e52024-08-22 · +147dVerified by operator
- New Hampshire State AGbd_5ff80c0e266b78012024-08-22 · +147dVerified
- Maine State AGbd_e66e6880aed1369a2024-08-22 · +147dCandidate
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Mar 28, last Aug 22 (ME) — a 147-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.