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

INGRAM MICRO INC. — July 2025 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Jan 16, 2026 → Jan 23, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

42,521

First → last dated filing

Jan 16, 2026 → Jan 23, 2026

Merge confidence

100%

incident inc_6a254ae953b049a8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 2, 2025–Jul 3, 2025, discovered Jul 3, 2025. 42,521 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 5 more. Notifications rolled out on a 7-day schedule across 7 dated filings beginning Jan 16, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
176days

Range of discovered_at dates across filings

Filing span
7days

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 bdayMassachusetts✗ MA AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 2, 2025breach begins
Jul 3, 2025discovered · members disagree
Jan 16, 2026first dated filing
Jan 23, 2026most 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. JUL 29Leak sitesafepay postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 16ME AGME AG noticestates nationwide total 42,521+170d
  4. JAN 16IN AGIN AG noticestates nationwide total 42,521+170d
  5. JAN 16NE AGNE AG noticefiling day not on record · no count stated—
  6. JAN 16VT AGVT AG noticeno count stated+170d
  7. JAN 16CA AGCA AG noticeno count stated+170d
  8. JAN 17MA AGMA AG notice139 MA residents+171d
  9. JAN 21TX AGTX AG noticestates nationwide total 42,521+175d
  10. JAN 23NH AGNH AG noticemost recent · 40 NH residents+177d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 2, 2025 – Jul 3, 2025
ME AG
Discovered
Jul 3, 2025NE AG + VT AG + MA AG +1Dec 26, 2025IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + NE AG + MA AG +5
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)

42,521

Sum of filed state slices

7,399· 17.4% of stated

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

US42,521
IN4,136
TX3,079
MA139
NH40
ME5

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 filing9 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 14, 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

7 days

Cadence

~1 / 1.2d

vs. multi-state median

1.2× 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.