NovoCure Limited
Clustered 4 records across 2 jurisdictions: 2 filings, 1 press report and 1 leak-site claim · filing window Sep 1, 2026 → Sep 9, 2026. View entity profile → Other incidents for this victim →
incident inc_773d33eef27b40f1 · merged by deterministic · confidence 100%
Litigation Timing
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — needs two dated filings.
Incident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing and leak-site claim in this incident
- AUG 22Leak siteshinyhunters postfirst record · attacker claim · unverifiedday 0
- SEP 1SEC 8-KSEC 8-K noticeno count statedauto-linked+10d
- SEP 9HHS OCRHHS OCR noticemost recent · states nationwide total 1,464auto-linked+18d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- —
- Discovered
- —
- Data types
- Health (basic) · Identity (basic) · PII SEC 8-K + HHS OCR
- Attack vector
- Unauthorized Access SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
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.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
8 days
vs. multi-state median
1.3× slower
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.