DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed14 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

Data Media Associates — May 2023 breach

Clustered 14 filings across 10 jurisdictions · filing window Aug 23, 2023 → Oct 9, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

10

Affected · reported

100,644

First → last filing

Aug 23, 2023 → Oct 9, 2023

Merge confidence

100%

incident inc_a9f5638440fa4f5c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion May 31, 2023–Jun 1, 2023, discovered Jun 1, 2023 — the first regulatory filing landed 83 days later (flagged late). 100,644 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 47-day schedule across 14 filings beginning Aug 23, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
83days

Discovered → first regulatory filing

Discovery variance
29days

Range of discovered_at dates across filings

Filing span
47days

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 clocksHIPAA✗ HHS report late · 101dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 54dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 31, 2023breach begins
Jun 1, 2023discovered · members disagree
notification delay · 83 days
Aug 23, 2023first filing
Oct 9, 2023most 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 23IN AGIN AG noticefirst filing · states nationwide total 98,496day 0
  2. AUG 23CA AGCA AG noticeno count statedday 0
  3. AUG 23MT AGMT AG notice33 MT residentsday 0
  4. AUG 23OR AGOR AG noticestates nationwide total 74,730day 0
  5. AUG 23DE AGDE AG noticeno count statedday 0
  6. AUG 23MA AGMA AG notice2,788 MA residentsday 0
  7. AUG 23ME AGME AG noticestates nationwide total 74,730day 0
  8. AUG 24HHS OCRHHS OCR noticestates nationwide total 100,644+1d
  9. AUG 28NH AGNH AG notice182 NH residents+5d
  10. AUG 30DE AGDE AG noticeno count stated+7d
  11. SEP 25MA AGMA AG notice2,793 MA residents+33d
  12. SEP 25WA AGWA AG notice657 WA residents+33d
  13. SEP 25ME AGME AG noticestates nationwide total 98,496+33d
  14. OCT 9HHS OCRHHS OCR noticemost recent · states nationwide total 2,035+47d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 31, 2023
IN AG
Discovered
Jun 1, 2023CA AG + MT AG + DE AGJun 4, 2023NH AG + WA AGJun 30, 2023ME AG + HHS OCRfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + MT AG + DE AG +5
Attack vector
Unauthorized Access
CA 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)

100,644

Sum of filed state slices

5,520· 5.5% of stated

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

US100,644
MA2,793
IN1,722
WA657
NH182
ME133
MT33

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 filing14 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 Aug 23, 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

47 days

Cadence

~1 / 3.6d

vs. multi-state median

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