Clustered 4 filings across 4 jurisdictions · filing window Aug 23, 2023 → Aug 30, 2023. View entity profile → Other incidents for this victim →
incident inc_4119e3a8884244d1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
DE GA MT OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 29, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 1, 2023
Reported by DELAWARE AG filing
Data Media Associates reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-23. The breach occurred from 5/29/2023 to 5/30/2023. 33 Montana residents were affected.
Affected (this filing): 33
Data Media Associates, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2023-08-23. 74,730 individuals were affected.
Affected (this filing): 74,730
Data Media Associates reported to HHS on 2023-08-24 a Hacking/IT Incident affecting 100,644 individuals. Breached information located on Network Server. A software application exposed PHI including names, addresses, SSNs, and health insurance info. The BA notified HHS, individuals, and media, and strengthened technical safeguards.
Affected (this filing): 100,644
Data Media Associates, LLC notified Delaware AG on August 23, 2023, of a data security incident involving the MOVEit Transfer software vulnerability. The incident, discovered in June 2023, potentially exposed protected health information (PHI) and personal data of individuals associated with DMA's healthcare clients. DMA patched the system, engaged external experts, and is notifying affected individuals.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.