GLOBALClaimed by RyukFirst sightinglinked via operator-confirmed · 100%
Posted to leak site May 6, 2019bd_7b913a86cadd0850
Clustered 3 filings across 2 jurisdictions · filing window May 6, 2019 → Mar 1, 2021. View entity profile → Other incidents for this victim →
incident inc_cff46cca55db486a · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
OR
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 6, 2019 → May 15, 2019
When the intrusion reportedly occurred, per the linked filings
Nov 24, 2020
Reported by OREGON AG filing
Metro Presort, Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2021-02-18. The breach occurred during 5/6/2019 - 5/15/2019. The breach was discovered on 11/24/2020. 24,100 individuals were affected. Notice was sent on 1/20/20211/22/2021.
Metro Presort, Inc. (OR), a business associate, reported to HHS OCR on 2021-03-01 a ransomware attack affecting 38,387 individuals' ePHI stored on a network server. Exposed data included names, dates of birth, addresses, diagnoses/conditions, and treatment information. Following an OCR investigation, the BA revised its HIPAA security procedures, retrained its workforce, and implemented additional technical safeguards. OCR provided technical assistance and received assurances of corrective action completion.
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.
Affected (this filing): 24,100
Affected (this filing): 38,387