Sierra Lobo, Inc.
bd_2c069e37d0b88f29 · schema v1 · pii pii-v1
Full breach record for Sierra Lobo, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
Sierra Lobo, Inc. specializes in providing test, evaluation and engineering services to the aerospace sector nationwide. We also offer in-house engineering and R&D services through our Technology Development and Engineering Center (TDEC) in northern Ohio.SITE: www.sierralobo.com Address : 102 Pinnacle Drive Fremont, OH 43420 USALL DATA SIZE: ~1.5tb 1. Accounting 2. Personal employees documents 3. Payroll 4. Projects and much more...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 23, 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 (2) · sorted by filing gap
- Massachusetts State AGbd_59ae1679a9f9ce8f2024-03-27 · +33dVerified
- Maine State AGbd_477e4020fb2bb9992024-03-28 · +34dCandidate
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Feb 23, last Mar 28 (ME) — a 34-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.