DisclosureLens
GLOBALMalwareHealthcareHealthcareRansomwareCl0pRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

NASCO

bd_8c1cb6cf621dcfa2 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Jul 12, 2023

To disclose

—

Affected

Not disclosed

Linked

17 records

Confidence

50%
Full breach record for NASCO →3 incidents on file

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.

Group activity: HealthcareDiscovered: 2023-07-12
View aggregator listing on ransomware.liveView merged incident timeline

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.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jul 12, 2023

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

This leak-site claim is one of 17 records about the same incident.View merged incident
Part of Progress Software Corporation supply-chain incident (2023) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (10) · sorted by filing gap

Show 6 more filings ↓up to 182d gap

Showing first 10 of 16 linked disclosures.

Filing propagation · 10 filings · 7 states

View merged incident ↗
Vermont State AGOct 27 · first
Oregon State AGOct 27 · first
California State AGOct 27 · first
Washington State AGOct 27 · first
Maine State AG+1d
South Carolina State AG+3d
New Hampshire State AG+7d
Vermont State AG+73d
Maine State AG+75d
California State AG+75d

Pattern: first filing Oct 27 (VT), last Jan 10 (CA) — a 75-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Cascade drawn from the first 10 linked disclosures of 16 — the full spread may be wider.

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.