OREGONMalwareHealthcareHealthcareRansomwareBusiness Associate (HIPAA)Customer Data InvolvedData EncryptedRansom DemandedHealth (basic)Identity (basic)MediumResolved

Metro Presort, Inc.

bd_0190d3b4c318032a · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 1, 2021

To disclose

—

Affected

38,387

Linked

3 filings

Confidence

91%

Full breach record for Metro Presort, Inc. →

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.

J jump to incidentP pin to compareR raw source

Leak gap clock✗ Leak >180d

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Mar 1, 2021

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 3 about the same incident.View merged incident

A leak claim by ryuk about this victim predates this filing by 665 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteryukbd_7b913a86cadd08502019-05-06 · +665dVerified by operator

Regulatory filings (1) · sorted by filing gap

Oregon State AGbd_14c6123c358738862021-02-18 · +11dVerified by operator

Name: Metro Presort, Inc.
norm: metro presort

Name: Metro Presort, Inc.
norm: metro presort
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 38,387nationwide
Data types: Health (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Business associate
Attack vector: Unauthorized Access
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: OCR investigation conducted; technical assistance provided; corrective action plan accepted with revised HIPAA security procedures, workforce retraining, and additional technical safeguards implemented.

During the incident: Notified HHS, affected individuals, and the media.
Revised HIPAA security procedures.
Retrained workforce members.
Implemented additional technical safeguards.
Changes made: Revised HIPAA security procedures.
Workforce retraining.
Additional technical safeguards implemented to protect systems maintaining ePHI.
Source: Quoted from the filing itself, not independently verified.

Compliance flags: Leak >180dHHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

Oregon State AGFeb 18 · first

HHS OCR+11d · this page

Pattern: first filing Feb 18 (OR), last Mar 1 (OR) — a 11-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Mar 1, 2021
Raw hash: a2edad6cc2641d7e9b42510f3080cc1d6c2bd267433240835d6e2eeed46e3652

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html1.6 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entityMetro Presort, Inc.

Victim entityMetro Presort, Inc.

IncidentUnauthorized Access

Stated responseNotified HHS, affected individuals, and the media.

ComplianceLeak >180d

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing