Barings LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-25. The breach occurred on 10/29/2023. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Mar 25, 2024. View entity profile → Other incidents for this victim →
incident inc_c2d5ef575c264a7f · merge_method llm · confidence 44%
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.
Identity (basic) · Government ID
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 29, 2023
When the intrusion reportedly occurred, per the linked filings
Jan 12, 2024
Reported by MAINE AG filing
Barings LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-25. The breach occurred on 10/29/2023. 2 Montana residents were affected.
Affected (this filing): 2
Barings LLC, a financial services company, reported a data breach to the Maine Attorney General. The breach, which occurred between October 29, 2023, and November 2, 2023, was an external system breach (hacking) discovered on January 12, 2024. The breach affected 2,671 individuals in total, including one resident of Maine. The compromised information includes names and Social Security Numbers. Barings LLC began notifying affected individuals on March 25, 2024, and is offering two years of complimentary credit monitoring and identity protection services through Experian.
Affected (this filing): 1
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.