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

Volume Transportation, Inc. — August 2025 breach

Clustered 5 records across 3 jurisdictions: 3 filings and 2 leak-site claims · filed Dec 8, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

3

Affected · reported

2,911

First → last filing

Dec 8, 2025

Merge confidence

100%

incident inc_2fc78da5468e4ca9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion Aug 18, 2025–Aug 19, 2025, discovered Aug 19, 2025 — the first regulatory filing landed 111 days later. 2,911 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
111days

Discovered → first regulatory filing

Leak precedence
86days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
0days

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.

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 111dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 18, 2025breach begins
Aug 19, 2025discovered
notification delay · 111 days
Dec 8, 2025first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

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

  1. AUG 14Leak siteqilin postfirst record · attacker claim · unverifiedday 0
  2. SEP 13Leak siteqilin postattacker claim · unverified+30d
  3. DEC 8IN AGIN AG noticestates nationwide total 2,911+116d
  4. DEC 8ME AGME AG noticestates nationwide total 2,911+116d
  5. DEC 8MA AGMA AG noticemost recent · 1 MA residents+116d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 18, 2025
IN AG
Discovered
Aug 19, 2025· 1d undetected
ME AG
Data types
Identity (basic) · Government ID
ME AG + MA AG
Attack vector
Unauthorized Access
ME 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)

2,911

Sum of filed state slices

11· 0.4% of stated

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

US2,911
IN9
ME1
MA1

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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
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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.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.