Houston Symphony
bd_86eee7489d4a0729 · schema v1 · pii pii-v1
Full breach record for Houston Symphony →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin 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
All data will be published on March 5, 2025.With over 300 GB of files stolen. During the 2019-20 season, the Houston Symphony celebrates its sixth season with Music Director Andrés Orozco-Estrada and continues its second century as one of Am ...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 28, 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 (4) · sorted by filing gap
- Indiana State AGbd_6beb0c1e6b1071ce2025-08-19 · +172dVerified by operator
- Nebraska State AGbd_d2adee11ef64e1272025-08-19 · +172dVerified
- Massachusetts State AGbd_db2092e68b9561ac2025-08-20 · +173dVerified by operator
- Texas State AGbd_5bed8bf384fff7b82025-08-22 · +175dVerified by operator
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Feb 28, last Aug 22 (TX) — a 175-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.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.