MalwareHealthcareTechnologyHealthcareRansomwareData ExfiltratedData EncryptedCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDHealth (basic)PHICriticalResolved

EpiSource

bd_63544f6aac5ae4a4 · schema v1 · pii pii-v1

Severity

Critical

Discovered

Feb 6, 2025

Filed

Jun 6, 2025

To disclose

17 weeks

Affected

102,913state residents only

Linked

24 filings

Confidence

70%

Full breach record for EpiSource →4 incidents on file

Episource, LLC reported a supplemental ransomware incident to the Washington AG. Unauthorized access occurred Jan 27–Feb 6, 2025, discovered Feb 6, 2025. 102,913 Washington residents affected. Data included PHI, SSNs, and PII. Notifications completed Feb 9, 2026. Credit monitoring offered.

J jump to incidentP pin to compareR raw source

Washington clock✗ WA AG >90d17 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 · 10 days

discovery → filing · 17 weeks / 120 days

Jan 27, 2025

Begins

Feb 6, 2025

Discovered

Jun 6, 2025

Filed

vs. sector median

+6 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (10) · sorted by filing gap

New Hampshire State AGbd_a2b82676192bff452025-09-15 · +101dVerified by operator
California State AGbd_9fdbc50e284e387e2025-09-22 · +108dVerified by operator
California State AGbd_f7b2fef6a5a68d492025-10-01 · +117dVerified by operator
California State AGbd_9fbf33f1d80fd6cd2025-10-15 · +131dVerified by operator

Show 6 more filings ↓up to 250d gap

California State AGbd_26b46fb1375699872025-11-12 · +159dVerified by operator
Montana State AGbd_8bfabd788a54c7dd2025-11-12 · +159dVerified by operator
Oregon State AGbd_a777c7526ecf94bd2025-12-11 · +188dVerified by operator
California State AGbd_e03b6cfce712071e2026-02-09 · +248dVerified by operator
New Hampshire State AGbd_5f78056b95d71c8e2026-02-10 · +249dVerified by operator
Texas State AGbd_902d3567da6db0052026-02-11 · +250dVerified by operator

Showing first 10 of 23 linked disclosures.

Name: EpiSource
norm: episource

Name: EpiSource
norm: episource
Industry: HealthcarellmTechnologyllm

Discovered: Feb 6, 2025
Breach occurred: Jan 27, 2025 – Feb 6, 2025
Undetected for: 10 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 9, 2026
Affected individuals: 102,913state-resident count only
Data types: Identity (basic)Government IDHealth (basic)PHI
Data elements: NameDate of birthHealth insurance IDMedical information
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified Washington Attorney General

During the incident: Hired a special team to help us
Called law enforcement
Turned off our computer systems to help protect our customers and their patients and members
Offering two (2) years of free credit monitoring and identity theft protection services
Changes made: Making our computer systems even stronger than before
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 weeks(120 days from discovery to filing)
Compliance flags: WA AG >90d
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 · 11 filings · 6 states

View merged incident ↗

Washington State AGJun 6 · first · this page

New Hampshire State AG+101d

California State AG+108d

California State AG+117d

California State AG+131d

California State AG+159d

Montana State AG+159d

Oregon State AG+188d

California State AG+248d

New Hampshire State AG+249d

Texas State AG+250d

Pattern: first filing Jun 6 (WA), last Feb 11 (TX) — a 250-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Cascade drawn from the first 10 linked disclosures of 23 — the full spread may be wider.

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/BreachA33536.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 6, 2025
Raw hash: 8599b34f8aa20ffc93e9826062be34499effcc54bc3300513c182e0a0003e04a

Linked disclosures

Regulatory filings (10) · sorted by filing gap

Reporting entityEpiSource

Victim entityEpiSource

Incidentdiscovered Feb 6, 2025

Stated responseHired a special team to help us

ComplianceWA AG >90d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com