International Business Machines Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-22. The breach occurred on 8/2/2023. 9,585 Montana residents were affected.
Affected (this filing): 9,585
Clustered 2 filings across 2 jurisdictions · filed Sep 22, 2023. View entity profile → Other incidents for this victim →
incident inc_01454cbb16314104 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 2, 2023
When the intrusion reportedly occurred, per the linked filings
Aug 2, 2023
Reported by CALIFORNIA AG filing
International Business Machines Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-22. The breach occurred on 8/2/2023. 9,585 Montana residents were affected.
Affected (this filing): 9,585
IBM disclosed unauthorized access to a database supporting the Janssen CarePath patient support platform. IBM identified the unauthorized access on August 2, 2023, after Janssen notified IBM of a technical method allowing access. IBM remediated the issue and augmented security controls. Affected data may include names and health-related information, but not SSNs or financial account data. IBM offered one year of credit monitoring.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.