Drummond Company Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-23 and was reported on 2026-03-31. 1 Indiana residents were affected. 1,398 individuals affected in total.
Affected (this filing): 1,398
Clustered 2 filings across 2 jurisdictions · filing window Mar 31, 2026 → Apr 14, 2026. View entity profile → Other incidents for this victim →
incident inc_258f94af1fa44b30 · 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.
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 23, 2026
When the intrusion reportedly occurred, per the linked filings
Feb 23, 2026
Reported by MAINE AG filing
Drummond Company Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-23 and was reported on 2026-03-31. 1 Indiana residents were affected. 1,398 individuals affected in total.
Affected (this filing): 1,398
Drummond Company, Inc. (Jasper, AL) reported an external system breach (hacking) to the Maine AG. The incident occurred on 02/20/2026 and was discovered on 02/23/2026. A total of 1,398 individuals were affected, including 1 Maine resident. Affected individuals were notified electronically on 03/31/2026 and offered 12 months of identity monitoring and consultation services through TransUnion. The submitted form did not specify the categories of personal information acquired.
Affected (this filing): 1,398
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.