All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed8 filings · 7 statesUnverified claimConfirmedEnforcedlockbit_3high sensitivity

Merged incident · 8 filings

Wabtec Corporation — March 2022 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 18, 2022 → Jan 4, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

7,415

First → last filing

Aug 18, 2022 → Jan 4, 2024

Merge confidence

100%

incident inc_70d097f2f392420a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. Intrusion Mar 15, 2022–Jun 26, 2022, discovered Mar 15, 2022 — the first regulatory filing landed 290 days later (flagged late). 7,415 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 504-day schedule across 7 filings beginning Aug 18, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

290days

Discovered → first regulatory filing

Discovery variance

253days

Range of discovered_at dates across filings

Leak precedence

134days 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

504days

Time between earliest and latest filing

Not recorded for this incident

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

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

Sensitive data

identity_government

Incident timeline

Mar 15, 2022breach begins

Mar 15, 2022discovered · members disagree

notification delay · 290 days

Dec 30, 2022first filing

Jan 4, 2024most recent filing

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

Member cascade — every filing about this breach

AUG 18Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
DEC 30MT AGMT AG notice6 MT residentsauto-linked+134d
DEC 30NH AGNH AG notice3 NH residentsauto-linked+134d
DEC 30IN AGIN AG noticestates nationwide total 7,415+134d
DEC 30ME AGME AG noticestates nationwide total 7,415auto-linked+134d
DEC 30MA AGMA AG notice7 MA residentsauto-linked+134d
JAN 1IL AGIL AG noticeno count statedauto-linked+501d
JAN 4CA AGCA AG noticemost recent · no count statedauto-linked+504d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 15, 2022
Discovered: Mar 15, 2022IL AGJun 26, 2022MT AG + NH AG + CA AGNov 23, 2022ME AGfilings disagree on discovery
Data types: Financial account · Identity (basic) · Government ID · PII
Attack vector: Ransomware

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)

7,415

Sum of filed state slices

81· 1.1% of stated

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

US7,415

IN63

MA7

MT6

NH3

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 claim1 member

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

504 days

Cadence

~1 / 72d

vs. multi-state median

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