NovoCure Limited
bd_05f89a4cca66d80e · schema v1 · pii pii-v2
Full breach record for NovoCure Limited →NovoCure Limited (CIK 0001645113) filed an 8-K on September 1, 2026, disclosing that in mid-August 2026 it became aware of unauthorized access to some of its information systems. The incident affected over 1,400 U.S. patient records (internal IDs) and fewer than 50 other patients with additional identifying data, plus healthcare provider and employee contact info. NovoCure engaged forensic experts and activated its response plan. The company stated no medical device access was obtained and operations remain functional, though it did not initially deem the incident material.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Sep 1, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteshinyhuntersbd_bdc9447f70280f082026-08-22 · +10dCandidate
Regulatory filings (1) · sorted by filing gap
- Pressshinyhuntersbd_1f4c992ee890e0092026-08-15 · +17dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Aug 15, last Sep 1 — a 17-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.