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

MSX INTERNATIONAL, INC. — February 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Feb 22, 2023 → Jul 20, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

13,113

First → last filing

Feb 22, 2023 → Jul 20, 2023

Merge confidence

100%

incident inc_604eb63a43f4463c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Feb 2, 2023–Feb 6, 2023, discovered Feb 6, 2023 — the first regulatory filing landed 163 days later (flagged late). 13,113 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 148-day schedule across 7 filings beginning Feb 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
163days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
147days before filing

Days between the first leak-site claim and the first regulatory filing. 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
148days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 60-day late · 164dMaine✗ ME AG >90d · 163dVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 2, 2023breach begins
Feb 6, 2023discovered
notification delay · 163 days
Jul 19, 2023first filing
Jul 20, 2023most 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. FEB 22Leak sitenokoyawa postfirst filing · attacker claim · unverifiedday 0
  2. FEB 27Leak sitesnatch postattacker claim · unverified+5d
  3. JUL 19CA AGCA AG noticeno count stated+147d
  4. JUL 19NH AGNH AG notice18 NH residents+147d
  5. JUL 19ME AGME AG noticestates nationwide total 13,113+147d
  6. JUL 19MT AGMT AG notice3 MT residents+147d
  7. JUL 19VT AGVT AG noticeno count stated+147d
  8. JUL 20MA AGMA AG notice61 MA residents+148d
  9. JUL 20IN AGIN AG noticemost recent · states nationwide total 13,113+148d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 2, 2023 – Feb 6, 2023
CA AG
Discovered
Feb 6, 2023· 4d undetected
CA AG + NH AG + ME AG +2
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
CA AG + NH AG + MT AG +3
Attack vector
Unauthorized Access
NH 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)

13,113

Sum of filed state slices

235· 1.8% of stated

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

US13,113
IN151
MA61
NH18
MT3
ME2

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 filing7 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 22, 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

148 days

Cadence

~1 / 18.5d

vs. multi-state median

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