HackingHealthcareHealthcareStolen CredentialsSupply Chain (3P Vendor)Customer Data InvolvedData ExfiltratedIdentity (basic)Health (basic)HighContained

Virginia Mason Medical Center

bd_0cdec261d8f9ad0c · schema v1 · pii pii-v1

Severity

High

Discovered

Jul 16, 2020

Filed

Sep 8, 2020

To disclose

8 weeks

Affected

227,371state residents only

Linked

3 filings

Confidence

70%

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

Virginia Mason Medical Center notified the Washington AG of a third-party vendor breach involving Blackbaud. Unauthorized access occurred Feb 7–May 20, 2020. VMMC discovered the incident on July 16, 2020. The breach exposed patient names, contact info, DOBs, and visit details for 227,371 Washington residents. No SSNs or financial data were accessed. VMMC mailed notices on Sept 8, 2020.

J jump to incidentP pin to compareR raw source

Washington clock⏱ WA AG >30d8 weeks discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 160 days

discovery → filing · 8 weeks / 54 days

Feb 7, 2020

Begins

Jul 16, 2020

Discovered

Sep 8, 2020

Filed

vs. sector median

1 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

HHS OCRbd_2cb27ab7bcdd40722020-09-08Verified
Illinois State AGbd_27fbeea8f5a2a5db2020-01-01 · +251dCandidate

Name: Virginia Mason Medical Center
norm: virginia mason medical center
Domain: virginiamason.org

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

Discovered: Jul 16, 2020
Breach occurred: Feb 7, 2020 – May 20, 2020
Undetected for: 160 daysoccurrence → discovery
Materiality determined: —
Notification sent: Sep 8, 2020
Affected individuals: 227,371state-resident count only
Data types: Identity (basic)Health (basic)
Data elements: NameDate of birth
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 100-199dexposure 100-199d
WA-stated discovery: Found after the fact
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain CompromiseT1078 Valid Accounts
Threat actor: External
Regulator citations: Submitted courtesy notification to the Office of the Washington Attorney General
Third party: via Blackbaud, Inc.
Initial access: external_remote_services

During the incident: Began mailing letters to the Washington residents on September 8, 2020
Established a dedicated, toll-free call center
Examining its vendor relationship with Blackbaud
Evaluating their security safeguards
Changes made: Blackbaud identified and fixed the vulnerability associated with this incident
Blackbaud is implementing additional security enhancements
VMMC is undertaking a review of how its information is stored with Blackbaud
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 weeks(54 days from discovery to filing)
Compliance flags: WA AG >30d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

Illinois State AGJan 1 · first

HHS OCR+251d

Washington State AG+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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM10300.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 8, 2020
Raw hash: 17cbf408a0e9eaf9cea50d0ebdef9cdbdc13f371dbe872bd1d2b87328de01ab7

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityVirginia Mason Medical Center

Victim entityVirginia Mason Medical Center

Incidentdiscovered Jul 16, 2020

Stated responseBegan mailing letters to the Washington residents on September 8, 2020

ComplianceWA AG >30d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com