DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

VACPARTSWAREHOUSE.COM — October 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window May 1, 2026 → May 22, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

23,820

First → last filing

May 1, 2026 → May 22, 2026

Merge confidence

100%

incident inc_9350f3df7a6644a7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Oct 31, 2025–Dec 12, 2025, discovered Oct 31, 2025 — the first regulatory filing landed 182 days later (flagged late). 23,820 individuals reported across the linked filings. Data reported: Financial account, Identity (basic), Financial credentials, and 2 more. Notifications rolled out on a 21-day schedule across 11 filings beginning May 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
182days

Discovered → first regulatory filing

Discovery variance
173days

Range of discovered_at dates across filings

Filing span
21days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 28dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Oct 31, 2025breach begins
Oct 31, 2025discovered · members disagree
notification delay · 182 days
May 1, 2026first filing
May 22, 2026most recent filing

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

Member cascade — every filing about this breach

  1. MAY 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 20OR AGOR AG noticestates nationwide total 23,820+19d
  3. MAY 20WA AGWA AG notice695 WA residents+19d
  4. MAY 20IN AGIN AG noticestates nationwide total 23,820+19d
  5. MAY 20NH AGNH AG notice221 NH residents+19d
  6. MAY 20CA AGCA AG noticeno count stated+19d
  7. MAY 20ME AGME AG notice238 ME residents+19d
  8. MAY 20MA AGMA AG notice703 MA residents+19d
  9. MAY 20VT AGVT AG notice139 VT residents+19d
  10. MAY 20NE AGNE AG notice186 NE residents+19d
  11. MAY 22TX AGTX AG noticemost recent · states nationwide total 23,820+21d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 31, 2025 – Dec 12, 2025
OR AG
Discovered
Oct 31, 2025WA AGApr 8, 2026OR AGApr 22, 2026IL AG + NH AG + ME AG +2filings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
IL AG + WA AG + NH AG +6
Attack vector
Unauthorized Access
WA 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)

23,820

Sum of filed state slices

4,277· 18.0% of stated

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

US23,820
TX1,559
MA703
WA695
IN536
ME238
NH221
NE186
VT139

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

21 days

Cadence

~1 / 2.1d

vs. multi-state median

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