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

Valsoft Corporation Inc. — February 2024 breach

Clustered 9 filings across 8 jurisdictions · filing window Feb 27, 2025 → May 6, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

161,359

First → last dated filing

Feb 27, 2025 → May 6, 2025

Merge confidence

100%

incident inc_531a29c4ac064126 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Feb 12, 2024–Feb 15, 2024, discovered Feb 12, 2024. 161,359 individuals reported across the linked filings. Data reported: Government ID, Financial account, Authentication, and 3 more. Notifications rolled out on a 68-day schedule across 8 dated filings beginning Feb 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
2days

Range of discovered_at dates across filings

Filing span
68days

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 >90dMaryland✗ MD AG >90dMaine⏱ ME AG >30d · 447dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Feb 12, 2024breach begins
Feb 12, 2024discovered · members disagree
Feb 27, 2025first dated filing
May 6, 2025most 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 about this breach

  1. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 27OR AGOR AG noticefirst filing · states nationwide total 98,123day 0
  3. FEB 27MA AGMA AG notice323 MA residentsday 0
  4. FEB 27WA AGWA AG notice3,185 WA residentsday 0
  5. FEB 27IN AGIN AG noticestates nationwide total 98,123day 0
  6. FEB 27MD AGMD AG notice668 MD residentsday 0
  7. FEB 27NH AGNH AG notice47 NH residentsday 0
  8. MAY 6NH AGNH AG notice49 NH residents+68d
  9. MAY 6ME AGME AG noticemost recent · states nationwide total 161,359+68d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2024 – Feb 15, 2024
WA AG
Discovered
Feb 12, 2024IL AGFeb 14, 2024WA AG + MD AG + NH AG +1filings disagree on discovery
Data types
Authentication · Credentials · Financial account · Identity (basic) · Government ID · PII
MA AG + WA AG + MD AG +2
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)

161,359

Sum of filed state slices

5,325· 3.3% of stated

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

US161,359
WA3,185
IN909
MD668
MA323
ME191
NH49

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

68 days

Cadence

~1 / 9.7d

vs. multi-state median

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