WASHINGTONMalwareHealthcareHealthcareRansomwareBusiness Associate (HIPAA)Customer Data InvolvedData EncryptedRansom DemandedHealth (basic)Identity (basic)HighResolved

Virginia Mason Medical Center

bd_2cb27ab7bcdd4072 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Sep 8, 2020

To disclose

—

Affected

244,761

Linked

3 filings

Confidence

97%

Full breach record for Virginia Mason Medical Center →3 incidents on file

Virginia Mason Medical Center (WA) reported to HHS on 2020-09-08 that its business associate experienced a ransomware attack affecting the ePHI of approximately 244,761 individuals. Breached information was located on a Network Server. Exposed data included names, addresses, dates of birth, and treatment information. The CE notified HHS, affected individuals, the media, and provided substitute notice.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ 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

Sep 8, 2020

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Washington State AGbd_0cdec261d8f9ad0c2020-09-08Verified
Illinois State AGbd_27fbeea8f5a2a5db2020-01-01 · +251dCandidate

Name: Virginia Mason Medical Center
norm: virginia mason medical center
Domain: virginiamason.org
Industry: Health Care Services

Name: Virginia Mason Medical Center
norm: virginia mason medical center
Domain: virginiamason.org
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 244,761nationwide
Data types: Health (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: HHS OCR notification

During the incident: Notified HHS
Notified affected individuals
Notified media
Provided substitute notice
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS 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 · 3 filings · 2 states

View merged incident ↗

Illinois State AGJan 1 · first

Washington State AG+251d

HHS OCR+251d · this page

Pattern: first filing Jan 1 (IL), last Sep 8 (WA) — a 251-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: Sep 8, 2020
Raw hash: 6bfce3f856f071c28f133f68da9ac6efd8407e59b33665ac9adce6465ade10de

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.4 KB

Download View at source

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityVirginia Mason Medical Center

Victim entityVirginia Mason Medical Center

IncidentUnauthorized Access

Stated responseNotified HHS

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing