STS Aviation Group
bd_be5fb20f507062ab · schema v1 · pii pii-v1
Full breach record for STS Aviation Group →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
STS Aviation Group is a service provider for the aviation industry. The company was founded in 1986 and is headquartered in Jensen Beach, Florida.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 27, 2023
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 (5) · sorted by filing gap
- Massachusetts State AGbd_03f91d0c715a79fa2024-06-06 · +192dVerified by operator
- Indiana State AGbd_12abd998cfd879632024-06-06 · +192dVerified
- New Hampshire State AGbd_1fc3b5a9995b107c2024-06-06 · +192dVerified
- Maine State AGbd_dd7b5193b2e665962024-06-06 · +192dCandidate
Show 1 more filing ↓Show fewer ↑up to 192d gap
- Montana State AGbd_e8f527f1c41f524a2024-06-06 · +192dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Nov 27, last Jun 6 (MT) — a 192-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.