DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 records · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 13 records

Trinity Petroleum Management, LLC — October 2024 breach

Clustered 13 records across 12 jurisdictions: 12 filings and 1 leak-site claim · filing window Mar 10, 2025 → Mar 12, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 records

States

12

Affected · reported

46,659

First → last dated filing

Mar 10, 2025 → Mar 12, 2025

Merge confidence

100%

incident inc_714e6ca14eeb4149 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 10, 2024–Oct 14, 2024, discovered Oct 14, 2024. 46,659 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
2days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayMaryland✗ MD AG >90dOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 122dWashington✗ WA AG >90dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 84dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 10, 2024breach begins
Oct 14, 2024discovered
Mar 10, 2025first dated filing
Mar 12, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. OCT 14Leak sitebianlian postfirst record · attacker claim · unverifiedday 0
  2. FEB 13NE AGNE AG noticefiling day not on record · no count stated—
  3. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  4. MAR 10IN AGIN AG noticestates nationwide total 46,659+147d
  5. MAR 10VT AGVT AG noticeno count stated+147d
  6. MAR 10MD AGMD AG notice130 MD residents+147d
  7. MAR 12MA AGMA AG notice130 MA residents+149d
  8. MAR 12NH AGNH AG notice34 NH residents+149d
  9. MAR 12MT AGMT AG notice768 MT residents+149d
  10. MAR 12OR AGOR AG noticestates nationwide total 46,659+149d
  11. MAR 12CA AGCA AG noticeno count stated+149d
  12. MAR 12ME AGME AG noticestates nationwide total 46,659+149d
  13. MAR 12WA AGWA AG noticemost recent · 748 WA residents+149d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 10, 2024 – Oct 14, 2024
NE AG
Discovered
Oct 14, 2024· 4d undetected
NE AG + IL AG + VT AG +7
Data types
Financial account · Identity (basic) · Government ID · PII
NE AG + VT AG + MD AG +6
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

46,659

Sum of filed state slices

2,013· 4.3% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US46,659
MT768
WA748
IN170
MD130
MA130
NH34
ME33

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

2 days

Cadence

~1 / 0.2d

vs. multi-state median

3.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.