MalwareTechnologyInformationRansomwareData EncryptedCustomer Data InvolvedFinancial accountIdentity (basic)Government IDPHIPIIHealth (basic)HighContained

MicroCODE™

bd_4268f4d69cb3f737 · schema v1 · pii pii-v1

Severity

High

Discovered

Apr 14, 2026

Filed

Jul 30, 2026

To disclose

15 weeks

Affected

4,096state residents only

Confidence

70%

Full breach record for MicroCODE™ →

Microcode, Inc. experienced a ransomware event on April 14, 2026, affecting a database hosting medical malpractice insurance tracking for CommonSpirit Health. Unauthorized access occurred between January 19 and April 14, 2026. Personal information (name, date of birth) was potentially compromised for 4,096 Washington residents. Microcode engaged forensic vendors and Kroll for customer support, and enhanced security controls.

J jump to incidentP pin to compareR raw source

Washington clock✗ WA AG >90d15 weeks discovery → filing

Incident timeline

undetected · 85 days

discovery → filing · 15 weeks / 107 days

Jan 19, 2026

Begins

Apr 14, 2026

Discovered

Jul 30, 2026

Filed

vs. sector median

3 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed4,096 affectedView incident

Name: MicroCODE™
norm: microcode
Domain: mcode.com

Name: MicroCODE™
norm: microcode
Domain: mcode.com
Industry: Technologyllm

Discovered: Apr 14, 2026
Breach occurred: Jan 19, 2026 – Apr 14, 2026
Undetected for: 85 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 4,096state-resident count only
Data types: PIIIdentity (basic)
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birthPassport numberMedical 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 Impact
Threat actor: ExternalFinancial

During the incident: Initiated an investigation with a forensic vendor
Worked with its forensic investigation and legal teams
Retained a third party, Kroll, to manage a call center
Changes made: Refined its systems, security controls, and practices
Enhancements designed to bolster access controls, network-level protections, monitoring capabilities, backup resilience, and ongoing security testing
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 15 weeks(107 days from discovery to filing)
Compliance flags: WA AG >90d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

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/BreachA42069.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 30, 2026
Raw hash: ca5ccac3e37655f3013074dfe031cad07d65e6ab6532650dffd5af9d448d9b8d

Reporting entityMicroCODE™

Victim entityMicroCODE™

Incidentdiscovered Apr 14, 2026

Stated responseInitiated an investigation with a forensic vendor

ComplianceWA AG >90d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com