Gannett Company, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2017-04-28. The breach occurred on 3/30/2017. 90 Montana residents were affected.
Affected (this filing): 90
Clustered 2 filings across 2 jurisdictions · filed Apr 28, 2017. View entity profile → Other incidents for this victim →
incident inc_cdc30e659c2b4115 · 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
Mar 30, 2017
When the intrusion reportedly occurred, per the linked filings
Mar 30, 2017
Reported by CALIFORNIA AG filing
Gannett Company, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2017-04-28. The breach occurred on 3/30/2017. 90 Montana residents were affected.
Affected (this filing): 90
Gannett Company, Inc. reported a data breach affecting California residents. On March 30, 2017, Gannett discovered a phishing attack compromised HR department Office 365 credentials. The attacker used these credentials to send further phishing emails and attempted a fraudulent wire transfer. While no sensitive data acquisition was confirmed, employee PII (names, SSNs, DOB, bank details, salary) was potentially accessible. Gannett locked accounts, conducted forensic investigations, notified law enforcement, and provided 12 months of AllClear ID identity protection to affected individuals.
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.