Social EngineeringHealthcareHealthcarePhishingCustomer Data InvolvedEmployee Data InvolvedTargetedFinancial accountHealth (basic)Identity (basic)Government IDPHIHighContained

Virginia Mason Medical Center

bd_4421f1d2aa984733 · schema v1 · pii pii-v1

Severity

High

Discovered

Jan 18, 2022

Filed

Feb 18, 2022

To disclose

4 weeks

Affected

3,000state residents only

Linked

2 filings

Confidence

70%

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

Virginia Mason Medical Center experienced a phishing attack between Dec 21, 2021 and Jan 3, 2022, compromising staff email accounts. The incident was discovered on Jan 18, 2022. Patient and employee data, including PHI, SSNs, and financial info, may have been accessed. 3,000 Washington residents were notified. VMMC reset credentials, blocked domains, and offered Kroll credit monitoring.

J jump to incidentP pin to compareR raw source

Washington clock⏱ WA AG >30d4 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 · 28 days

discovery → filing · 4 weeks / 31 days

Dec 21, 2021

Begins

Jan 18, 2022

Discovered

Feb 18, 2022

Filed

vs. sector median

7 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCRbd_d80e254a4ed786a22022-03-14 · +24dCandidate

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: Jan 18, 2022
Breach occurred: Dec 21, 2021 – Jan 3, 2022
Undetected for: 28 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 3,000state-resident count only
Data types: Identity (basic)Government IDHealth (basic)Financial account
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birthPassport numberHealth insurance IDMedical information
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found after the fact
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid AccountsT1114 Email Collection
Threat actor: ExternalFinancial
Initial access: phishing_link

During the incident: Blocks to the phishing domain were quickly put in place
Credentials and passwords were reset
Suspicious activity was quarantined
Staff will also be reeducated on steps to ensure the security of protected information, and to guard against phishing attacks
VMMC reviewed every email involved to determine the information that may have been present
Changes made: Staff will also be reeducated on steps to ensure the security of protected information, and to guard against phishing attacks
Secured the services of Kroll to provide identity monitoring at no cost to patient’s and employees for one year
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 4 weeks(31 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 · 2 filings

View merged incident ↗

Washington State AGFeb 18 · first · this page

HHS OCR+24d

Pattern: first filing Feb 18 (WA), last Mar 14 (WA) — a 24-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/BreachA5341.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 18, 2022
Raw hash: 1fe2f3eb93b4dee71a673fed453646268be14e2a988055ad2611bfeaf5aa40d2

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityVirginia Mason Medical Center

Victim entityVirginia Mason Medical Center

Incidentdiscovered Jan 18, 2022

Stated responseBlocks to the phishing domain were quickly put in place

ComplianceWA AG >30d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com