DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusahigh sensitivity
Merged incident · 10 records

PRESTIGE MAINTENANCE USA, LTD. — January 2025 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Jul 22, 2025 → Jul 24, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

65,642

First → last dated filing

Jul 22, 2025 → Jul 24, 2025

Merge confidence

100%

incident inc_b1bb05aad6784f33 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 17, 2025, discovered Jan 17, 2025. 65,642 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
178days

Range of discovered_at dates across filings

Filing span
2days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 186dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 17, 2025breach begins
Jan 17, 2025discovered · members disagree
Jul 22, 2025first dated filing
Jul 24, 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 and leak-site claim in this incident

  1. JAN 15Leak sitemedusa postfirst record · attacker claim · unverifiedday 0
  2. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 22NH AGNH AG notice2 NH residents+187d
  4. JUL 22IA AGIA AG notice972 IA residents+187d
  5. JUL 22IN AGIN AG noticestates nationwide total 65,642+187d
  6. JUL 22CA AGCA AG noticeno count stated+187d
  7. JUL 22NE AGNE AG noticefiling day not on record · 598 NE residents—
  8. JUL 22ME AGME AG noticestates nationwide total 65,452+187d
  9. JUL 24MA AGMA AG notice12 MA residents+189d
  10. JUL 24TX AGTX AG noticemost recent · states nationwide total 65,452+189d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 17, 2025
IN AG
Discovered
Jan 17, 2025NH AG + IA AG + CA AG +2Jul 14, 2025IL AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
IL AG + MA AG + TX AG +5
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)

65,642

Sum of filed state slices

18,373· 28.0% of stated

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

US65,642
TX15,360
IN1,428
IA972
NE598
MA12
NH2
ME1

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 29, 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

2 days

Cadence

~1 / 0.3d

vs. multi-state median

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