DisclosureLens
FEDERALItem 8.01 · voluntaryHackingHealthcareTechnologyHealthcareCustomer Data InvolvedPIIIdentity (basic)LowActive

NovoCure Limited

bd_05f89a4cca66d80e · schema v1 · pii pii-v2

Severity

Low

Discovered

—

Filed

Sep 1, 2026

To disclose

—

Affected

0

Linked

4 records

Confidence

66%
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.

Incident timeline — partial

? — ?

Breach window unknown

Sep 1, 2026

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 4 records about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Press reports (1)

Filing propagation · 2 filings

View merged incident ↗
SEC 8-KSep 1 · first · this page

Pattern: first filing Sep 1, last Sep 9 (PA) — a 8-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

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 statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.