Confirmed breach. Intrusion Oct 10, 2024–Oct 14, 2024, discovered Oct 14, 2024 — the first regulatory filing landed 147 days later. 46,659 individuals reported across the linked filings.
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.
Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
46,659
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 10, 2024
When the intrusion reportedly occurred, per the linked filings
Trinity Petroleum Management LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-10 and was reported on 2025-03-10. 170 Indiana residents were affected. 46,659 individuals affected in total.
Affected (this filing): 46,659
Leak >90d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Trinity Petroleum Management, LLC, an accounting service provider, reported a data security incident affecting 34 New Hampshire residents. Unauthorized access occurred between October 10 and October 14, 2024. The company retained forensic specialists, reset passwords, implemented MFA, and offered credit monitoring.
Affected (this filing): 34
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.