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

Navistar, Inc. — May 2021 breach

Clustered 9 records across 7 jurisdictions: 8 filings and 1 leak-site claim · filing window Jul 2, 2021 → Sep 27, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 records

States

7

Affected · reported

63,126

First → last dated filing

Jul 2, 2021 → Sep 27, 2021

Merge confidence

100%

incident inc_1e27e28df39148e0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 20, 2021, discovered May 20, 2021. 63,126 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 87-day schedule across 6 dated filings beginning Jul 2, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
92days

Range of discovered_at dates across filings

Filing span
87days

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 clocksMaine⏱ ME AG >30d · 31dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 20, 2021breach begins
May 20, 2021discovered · members disagree
Jul 2, 2021first dated filing
Sep 27, 2021most 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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 2MA AGMA AG noticefirst filing · 74 MA residentsday 0
  4. JUL 6IN AGIN AG noticestates nationwide total 63,126+4d
  5. SEP 20ME AGME AG noticestates nationwide total 63,126+80d
  6. SEP 21CA AGCA AG noticeno count stated+81d
  7. SEP 21MT AGMT AG notice32 MT residents+81d
  8. SEP 27NH AGNH AG notice22 NH residents+87d
  9. DEC 7Leak sitemarketo postmost recent · attacker claim · unverified+158d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 20, 2021
IN AG
Discovered
May 20, 2021IL AG + CA AG + MT AG +1Aug 20, 2021ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
MA AG + ME AG + CA AG +2
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)

63,126

Sum of filed state slices

12,336· 19.5% of stated

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

US63,126
IN12,171
MA74
ME37
MT32
NH22

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 filing8 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

87 days

Cadence

~1 / 17.4d

vs. multi-state median

14.5× slower

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.