MalwareOtherRansomwareRansom DemandedData EncryptedIdentity (basic)PHIMedium

Baylor Genetics

bd_193cb78de44702b9 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Jun 15, 2026

Filed

Aug 14, 2026

To disclose

9 weeks

Affected

27,243state residents only

Linked

8 filings

Confidence

95%

Full breach record for Baylor Genetics →3 incidents on file

Baylor Genetics, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2026-06-15 and filed notice on 2026-08-14. 27,243 Washington residents were affected. 60 days elapsed between awareness and notification. 4 days to identify the breach. 2 days to contain the breach.

J jump to incidentP pin to compareR raw source

Washington clock⏱ WA AG >30d9 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

discovery → filing · 9 weeks / 60 days

Jun 15, 2026

Discovered

Aug 14, 2026

Filed

vs. sector median

+1 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (7) · sorted by filing gap

New Hampshire State AGbd_1a86904b6a4514042026-08-14Verified
California State AGbd_3a92bcfd70212d9c2026-08-14Verified
HHS OCRbd_562f9a8d2ceb0a5d2026-08-14Verified
Vermont State AGbd_fc2c220468d5dac32026-08-14Verified

Show 3 more filings ↓up to 13d gap

Texas State AGbd_7c1ceae65408ebdf2026-08-18 · +4dVerified
Massachusetts State AGbd_51ce33da3d6256302026-08-01 · +13dVerified
Illinois State AGbd_756d042601769b1f2026-08-01 · +13dVerified

Name: Baylor Genetics
norm: baylor genetics

Name: Baylor Genetics
norm: baylor genetics
Industry: Otherllm

Discovered: Jun 15, 2026
Materiality determined: —
Notification sent: —
Affected individuals: 27,243state-resident count only
Data types: Identity (basic)PHI
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found while ongoing
Attack vector: Ransomware
Threat actor: ExternalFinancial

Time to disclose: 9 weeks(60 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 · 8 filings · 7 states

View merged incident ↗

Massachusetts State AGAug 1 · first

Illinois State AGAug 1 · first

New Hampshire State AG+13d

California State AG+13d

HHS OCR+13d

Vermont State AG+13d

Washington State AG+13d · this page

Texas State AG+17d

Pattern: first filing Aug 1 (MA), last Aug 18 (TX) — a 17-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://data.wa.gov/resource/sb4j-ca4h.json?id=25118
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 14, 2026
Raw hash: 4d3453864aed00114b8203ef9db80554e8efe99c6a2bd8c0d200b33e23e1b939

Linked disclosures

Regulatory filings (7) · sorted by filing gap

Reporting entityBaylor Genetics

Victim entityBaylor Genetics

Incidentdiscovered Jun 15, 2026

ComplianceWA AG >30d

Extraction provenanceno artifact recorded

Source provenancedata.wa.gov