Lowe Engineers
bd_db5a4a611096e7f2 · schema v1 · pii pii-v1
Full breach record for Lowe Engineers →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lynx 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.
Source: Ransomware.live
Post text · scraped from the leak site
The full intimate photos of IT director Loweengineers(Linda Messing) as well as 259gb of Loweengineers confidential DATA will be released 01.20.2025
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 15, 2025
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 (2) · sorted by filing gap
- Nebraska State AGbd_04672c37905820452025-10-09 · +266dVerified
- Massachusetts State AGbd_84c934bf3131a51a2025-10-09 · +266dVerified by operator
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Jan 15, last Oct 9 (MA) — a 266-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.
lynx
According to ransomware.live, Lynx is a ransomware-as-a-service operation that emerged in mid-2024 as a rebrand of INC Ransomware (whose source code was sold for $300,000 on the RAMP forum), claiming ~300 victims across manufacturing, business services, technology, and transportation with an 80/20 profit split for affiliates.