NASCO Industries Inc
bd_8c1cb6cf621dcfa2 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p 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
NASCO – NASCO is a healthcare company dedicated to co-creating digital health solutions for Blue Cross and Blue Shield companies.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 12, 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 (6) · sorted by filing gap
- Oregon State AGbd_aa31f139773717df2023-10-27 · +107dVerified
- Washington State AGbd_f61696cdfa81c4df2023-10-27 · +107dVerified by operator
- Montana State AGbd_ffb048d919d7530a2023-10-27 · +107dVerified by operator
- Maine State AGbd_27541ee9c5b7e6e72023-10-28 · +108dCandidate
Show 2 more filings ↓Show fewer ↑up to 192d gap
- South Carolina State AGbd_1a92f137101f29bd2023-10-30 · +110dVerified
- Illinois State AGbd_1bc42ec569be8ced2023-01-01 · +192dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Oct 30 (SC) — a 302-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.