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

Print Media Association — May 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Sep 1, 2025 → Sep 10, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

20,378

First → last filing

Sep 1, 2025 → Sep 10, 2025

Merge confidence

100%

incident inc_094e64f266eb4e29 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion May 1, 2025–May 5, 2025, discovered May 5, 2025 — the first regulatory filing landed 119 days later (flagged late). 20,378 individuals reported across the linked filings. Data reported: Biometric, Government ID, Financial account, and 4 more. Notifications rolled out on a 9-day schedule across 9 filings beginning Sep 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
119days

Discovered → first regulatory filing

Discovery variance
98days

Range of discovered_at dates across filings

Filing span
9days

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 clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 128dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

May 1, 2025breach begins
May 5, 2025discovered · members disagree
notification delay · 119 days
Sep 1, 2025first filing
Sep 10, 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. SEP 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 10VT AGVT AG noticeno count stated+9d
  3. SEP 10MA AGMA AG notice258 MA residents+9d
  4. SEP 10IN AGIN AG noticestates nationwide total 20,378+9d
  5. SEP 10NH AGNH AG notice3 NH residents+9d
  6. SEP 10CA AGCA AG noticeno count stated+9d
  7. SEP 10NE AGNE AG notice67 NE residents+9d
  8. SEP 10TX AGTX AG noticestates nationwide total 20,378+9d
  9. SEP 10ME AGME AG noticemost recent · 2 ME residents+9d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2025 – May 5, 2025
VT AG
Discovered
May 5, 2025VT AG + NH AG + CA AG +2Aug 11, 2025IL AG + TX AGfilings disagree on discovery
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + NE AG +5
Attack vector
Unauthorized Access
VT 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)

20,378

Sum of filed state slices

3,799· 18.6% of stated

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

US20,378
TX3,085
IN384
MA258
NE67
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 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
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

9 days

Cadence

~1 / 1.1d

vs. multi-state median

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