DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 8 filings

Form I-9 Compliance — February 2024 breach

Clustered 8 filings across 7 jurisdictions · filing window Oct 11, 2024 → Nov 7, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

193,612

First → last filing

Oct 11, 2024 → Nov 7, 2024

Merge confidence

100%

incident inc_d393d5cd93374a4e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Feb 5, 2024–Apr 12, 2024, discovered Apr 12, 2024 — the first regulatory filing landed 182 days later (flagged late). 193,612 individuals reported across the linked filings. Data reported: Government ID, Biometric, and Identity (basic). Notifications rolled out on a 27-day schedule across 8 filings beginning Oct 11, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
182days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
27days

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 clocksMaine✗ ME AG >90d · 182dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dWashington✗ WA AG >90dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Feb 5, 2024breach begins
Apr 12, 2024discovered
notification delay · 182 days
Oct 11, 2024first filing
Nov 7, 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

  1. OCT 11ME AGME AG noticefirst filing · states nationwide total 96,982day 0
  2. OCT 11CA AGCA AG noticeno count statedday 0
  3. OCT 12VT AGVT AG noticeno count stated+1d
  4. OCT 15NH AGNH AG notice72 NH residents+4d
  5. OCT 16OR AGOR AG noticestates nationwide total 169,200+5d
  6. OCT 16WA AGWA AG notice2,852 WA residents+5d
  7. OCT 17SC AGSC AG notice3,514 SC residents+6d
  8. NOV 7ME AGME AG noticemost recent · states nationwide total 193,612+27d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 5, 2024 – Apr 12, 2024
ME AG
Discovered
Apr 12, 2024· 67d undetected
ME AG + CA AG + VT AG +4
Data types
Biometric · Identity (basic) · Government ID
ME AG + CA AG + VT AG +3
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)

193,612

Sum of filed state slices

6,621· 3.4% of stated

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

US193,612
SC3,514
WA2,852
ME183
NH72

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

27 days

Cadence

~1 / 3.9d

vs. multi-state median

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