Wings Etc.
bd_470539b626d9a563 · schema v1 · pii pii-v1
Full breach record for Wings Etc. →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Unsafe 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
country: US - revenue: 145.00M
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 21, 2022
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- Idaho State AGbd_d52cefc3da85d1012022-12-31 · +10dCandidate
- Massachusetts State AGbd_d0e18893f0462fea2023-01-31 · +41dVerified by operator
Filing propagation · 2 filings · 2 states
View merged incident ↗Pattern: first filing Dec 31 (ID), last Jan 31 (MA) — a 31-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.
unsafe
According to ransomware.live, A group which seems to recycle leak from other ransomware groups