Clustered 3 filings across 3 jurisdictions · filing window Feb 19, 2025 → Feb 4, 2026. View entity profile → Other incidents for this victim →
incident inc_3d7e4156aabb4b39 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Started in 1969 and headquartered in Memphis, Tennessee, Barnhart is a heavy lift and heavy transport company. The company offers a variety of heavy lift and transport services across the United States, including operated crane rental, rigging services, component replacement solutions, industrial storage, and more
Aug 27, 2025 → Aug 29, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 29, 2025
Reported by VERMONT AG filing
Barnhart Group, Inc. notified consumers of unauthorized access to network data between August 27-29, 2025. The incident involved names combined with other identifiers. The company engaged law enforcement and forensic specialists, secured systems, and offered 12 months of credit monitoring and fraud assistance. Notification was sent in February 2026.
Barnhart Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-27 and was reported on 2026-02-04. 3 Indiana residents were affected. 1,435 individuals affected in total.
Affected (this filing):
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.