Metro Presort, Inc.
bd_7b913a86cadd0850 · schema v1 · pii pii-v1
Full breach record for Metro Presort, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Ryuk on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 6, 2019
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- Oregon State AGbd_14c6123c358738862021-02-18 · +654dVerified by operator
- HHS OCRbd_0190d3b4c318032a2021-03-01 · +665dVerified by operator
Filing propagation · 2 filings
View merged incident ↗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
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.