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

Lasership Inc. — April 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Aug 27, 2025 → Aug 28, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

40,018

First → last filing

Aug 27, 2025 → Aug 28, 2025

Merge confidence

100%

incident inc_cdfd9bc24c21405c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Apr 13, 2025–Apr 15, 2025, discovered Apr 15, 2025 — the first regulatory filing landed 134 days later (flagged late). 40,018 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
134days

Discovered → first regulatory filing

Discovery variance
104days

Range of discovered_at dates across filings

Filing span
1days

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 ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 13, 2025breach begins
Apr 15, 2025discovered · members disagree
notification delay · 134 days
Aug 27, 2025first filing
Aug 28, 2025most 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. AUG 27IN AGIN AG noticefirst filing · states nationwide total 40,017day 0
  2. AUG 27OR AGOR AG noticestates nationwide total 40,018day 0
  3. AUG 27NE AGNE AG noticeno count statedday 0
  4. AUG 27MT AGMT AG notice1 MT residentsday 0
  5. AUG 27CA AGCA AG noticeno count statedday 0
  6. AUG 27WA AGWA AG notice3,267 WA residentsday 0
  7. AUG 27VT AGVT AG notice1 VT residentsday 0
  8. AUG 28TX AGTX AG noticestates nationwide total 40,018+1d
  9. AUG 28MA AGMA AG notice28 MA residents+1d
  10. AUG 28NH AGNH AG noticemost recent · 3 NH residents+1d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 13, 2025
IN AG
Discovered
Apr 15, 2025WA AG + NH AGJul 28, 2025OR AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NE AG + MT AG + CA AG +5
Attack vector
Unauthorized Access
MT 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)

40,018

Sum of filed state slices

3,934· 9.8% of stated

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

US40,018
WA3,267
TX559
IN75
MA28
NH3
MT1
VT1

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

8.0× faster

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.