Clustered 3 filings across 3 jurisdictions · filing window Jul 27, 2021 → Sep 11, 2021. View entity profile → Other incidents for this victim →
incident inc_db45abf308f248a3 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA ME MT
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 18, 2021
Reported by CALIFORNIA AG, MAINE AG filings
May 24, 2021
When the intrusion reportedly occurred, per the linked filings
Carpenter Co. reported a data breach to the Montana Attorney General. The breach was reported on 2021-07-27. The breach occurred on 5/24/2021. 4 Montana residents were affected.
Affected (this filing): 4
Carpenter Co experienced a ransomware incident on March 18, 2021, impacting IT systems. The company did not pay the ransom. Forensic investigation confirmed on May 24, 2021, that threat actors accessed personal information of employees and contractors, including SSNs, DOBs, financial account details, and health information. The company contained the malware, locked out unauthorized users, and engaged forensic experts. Remediation included network monitoring and active directory hardening. Identity monitoring was provided via Kroll.
Carpenter Co. experienced an external system breach on March 18, 2021, which was discovered the same day. The breach affected approximately 14,300 individuals, including 5 Maine residents, and compromised their names and Social Security numbers. In response, the company offered a 12-month membership to Kroll’s credit monitoring and identity theft restoration services.
Affected (this filing): 5
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.