# Mon General Hospital (West Virginia) Notifies Patients After May 2026 Phishing Attack Compromises Employee Email Accounts, Exposing PHI/PII Including Social Security Numbers

> Monongalia County General Hospital Company (Mon General, West Virginia) discovered on May 6, 2026 that a phishing attack had compromised a small number of employee email accounts; unauthorized access was terminated the same day. An investigation concluded in late June 2026 found the attacker may have accessed patient names, dates of birth, email addresses, phone numbers, Social Security numbers, and health/health insurance information, with no other data storage or hospital systems affected.

- **Published:** 2026-08-01T00:00:00Z
- **Last reviewed:** 2026-08-01T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1810
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-mon-general-2026-phishing-breach-tl-2026-1810.webp?v=cbdfb72b (Threadlinqs threat intel: Mon General Hospital Email Compromise: Detection & IOCs (TL-2026-1810) — High severity, 20 IOCs, 9 detection rules.)
- **ID:** TL-2026-1810
- **Severity:** HIGH
- **Category:** DATA_BREACH
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 20

## Description

On May 6, 2026, Mon General (Monongalia County General Hospital Company), part of Monongalia Health System, Inc. in Morgantown, West Virginia, identified that a phishing attack had targeted and compromised a small number of employee email accounts. The hospital states it terminated unauthorized access to the affected mailboxes the same day it was discovered and engaged an external cybersecurity/forensic firm to investigate, reset user credentials, and evaluate additional technical safeguards. The investigation, which concluded in late June 2026, determined that the compromise was confined to the small number of email accounts identified and did not extend to any other data storage system or hospital IT system (electronic health records were not implicated). Investigators determined the attacker may have been able to view patient first and last names, dates of birth, email addresses, phone numbers, Social Security numbers, and health or health insurance information contained in or attached to the compromised mailboxes. Mon General began mailing notification letters to affected patients around late July/early August 2026, offering two years of complimentary credit monitoring and operating a dedicated toll-free helpline (844-958-8936; WDTV states Mon-Fri 8:00am-5:30pm, WAJR states Mon-Fri 9:00am-6:30pm — hours differ slightly across corroborating outlets) for patient questions. No CVE, malware family, exploit, or specific threat-actor attribution has been disclosed in any public reporting; this is a breach-notification-driven disclosure rather than a technical vulnerability advisory, so exploit-chain and infrastructure detail is limited to what the hospital and corroborating outlets have stated.

Notably, this is not the first email-based compromise at this health system. In a separate, unrelated pair of 2021 incidents, unauthorized individuals accessed a Monongalia Health System contractor's email account between May 10 and August 15, 2021, and used it to send fraudulent wire-transfer requests (T1657 Financial Theft) and conduct further phishing; the intrusion was discovered in late July 2021 (around July 28) only when a vendor reported not receiving an expected payment. Affected organizations named in that 2021 disclosure include Monongalia Health System, Inc., Monongalia County General Hospital Company, and Stonewall Jackson Memorial Hospital Company (two other affiliated facilities, Mon Health Preston Memorial Hospital and Mon Health Marion Neighborhood Hospital, were confirmed NOT involved). That breach exposed PHI/PII — names, addresses, Social Security numbers, Medicare Health Insurance Claim numbers, dates of birth, patient account numbers, health-plan member IDs, medical record numbers, service dates, provider names, and claims/clinical treatment data — for approximately 398,164 patients, and was disclosed to patients beginning December 21, 2021 (reported publicly December 23, 2021). The organization stated it subsequently implemented multi-factor authentication for remote email access as a corrective measure following that incident. The recurrence of an employee-email-account compromise via phishing at the same health system in 2026 — years after MFA was reportedly deployed as a remediation for the 2021 incident — is a notable pattern worth flagging for correlation and defensive tracking, though public reporting on the 2026 incident does not disclose whether MFA was bypassed, not enforced for the affected accounts, or not a factor at all.

The incident sits within a well-documented healthcare-sector threat landscape. HHS's Health Sector Cybersecurity Coordination Center (HC3) has repeatedly warned that phishing and business email compromise (BEC) are among the most common and most financially damaging attack vectors against healthcare organizations: one HC3 sector alert documented over $50.8 billion in BEC losses affecting healthcare between October 2013 and December 2022, with 2023-2024 median per-incident losses near $50,000 and incidents spanning victims in 186 countries; the alert names CEO-fraud impersonation, false-invoice schemes, and data-theft social engineering as the dominant BEC sub-patterns and recommends separation-of-duties controls (independent second-employee verification) as a primary mitigation. Separately, Phishing-as-a-Service (PhaaS) kits such as RaccoonO365 (tracked by Microsoft as Storm-2246, operated by Nigeria-based Joshua Ogundipe) industrialized credential theft against Microsoft 365 mailboxes: the kit can process up to 9,000 target email addresses per day, uses spoofed Microsoft branding and infrastructure registered under fictitious identities to evade detection, and is documented by Microsoft as employing techniques to circumvent multi-factor-authentication protections (i.e., adversary-in-the-middle / reverse-proxy credential-and-session-cookie relay, T1557 / T1539) — harvesting an estimated 5,000+ credentials across 94 countries and targeting at least 20 U.S. healthcare organizations and a 2,300-organization U.S. tax-themed campaign before Microsoft's Digital Crimes Unit and Cloudflare obtained a U.S. federal court order and seized 338 associated domains in September 2025. There is no public evidence tying RaccoonO365, Storm-2246, or any specific PhaaS kit or actor to the Mon General incident; it is cited here as sector-relevant TTP/infrastructure context for the attack class (phishing leading to cloud-mailbox account takeover and PHI exposure at a U.S. hospital), not as a confirmed attribution.

## MITRE ATT&CK

- T1589 Gather Victim Identity Information
- T1598 Phishing for Information
- T1583 Acquire Infrastructure
- T1586 Compromise Accounts
- T1566 Phishing
- T1539 Steal Web Session Cookie
- T1557 Adversary-in-the-Middle
- T1078 Valid Accounts
- T1078 Valid Accounts
- T1078 Valid Accounts
- T1684.001 Impersonation
- T1087 Account Discovery
- T1114 Email Collection
- T1567 Exfiltration Over Web Service
- T1657 Financial Theft

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**AiTM Session-Cookie Replay — Risky Sign-In Without Fresh MFA Challenge** (`TL-2026-1810-SPL-001`)

Detects Microsoft 365 / Azure AD sign-ins that Conditional Access flagged as risky (atRisk / medium-high risk level) but that nonetheless succeeded via singleFactorAuthentication — the signature of a reverse-proxy AiTM phishing kit (RaccoonO365/Storm-2246-class) relaying a stolen session cookie to bypass MFA, as documented for the healthcare-sector attack class behind the Mon General mailbox compromise (TL-2026-1810).

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1557, T1539, T1078.004
- **Data sources:** azure_ad_signin_logs, o365_management_activity_azuread, conditional_access_logs
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
index=azure_ad sourcetype="azure:aad:signin" ResultType=0
| eval risky=if(match(RiskState,"(?i)atrisk") OR match(RiskLevelDuringSignIn,"(?i)(medium|high)"),1,0)
| eval single_factor=if(match(AuthenticationRequirement,"(?i)singlefactorauthentication"),1,0)
| where risky=1 AND single_factor=1
| stats count min(_time) as first_seen max(_time) as last_seen values(IPAddress) as src_ips values(Location) as locations values(AppDisplayName) as apps by UserPrincipalName
| where count>=1
| convert ctime(first_seen) ctime(last_seen)
| table UserPrincipalName, apps, src_ips, locations, count, first_seen, last_seen
```

### Microsoft KQL

```kql
SigninLogs
| where TimeGenerated > ago(24h)
| where ResultType == 0
| where RiskState == "atRisk" or RiskLevelDuringSignIn in ("medium","high")
| where AuthenticationRequirement == "singleFactorAuthentication"
| project TimeGenerated, UserPrincipalName, IPAddress, Location, AppDisplayName, RiskState, RiskLevelDuringSignIn, ConditionalAccessStatus
| order by TimeGenerated desc
```

### Sigma

```yaml
title: AiTM Session-Cookie Reuse Sign-In Without Fresh MFA
id: a1b2c3d4-1810-4001-9abc-000000000001
status: experimental
description: Detects a risky Azure AD sign-in that succeeds via singleFactorAuthentication, consistent with adversary-in-the-middle session-cookie replay bypassing MFA (RaccoonO365/Storm-2246-class PhaaS tradecraft).
references:
    - https://blogs.microsoft.com/on-the-issues/2025/09/16/microsoft-seizes-338-websites-to-disrupt-rapidly-growing-raccoono365-phishing-service/
author: Threadlinqs Team
date: 2026-08-02
tags:
    - attack.credential_access
    - attack.t1557
    - attack.t1539
    - attack.t1078.004
    - attack.tool.raccoono365
logsource:
    product: m365
    service: azuread
category: signin
detection:
    selection:
        ResultType: 0
        RiskState: 'atRisk'
        AuthenticationRequirement: 'singleFactorAuthentication'
    condition: selection
falsepositives:
    - Trusted-network or conditional-access-exempt sign-ins misclassified as risky
    - Legacy break-glass accounts intentionally exempted from MFA
level: critical
```

**Known false positives:**

- Legitimate sign-in from a trusted network or device exempted from Conditional Access risk scoring
- Break-glass/emergency-access accounts intentionally excluded from MFA enforcement

**Tuning notes:** Exclude known break-glass accounts and trusted-network CIDR ranges from the risky-sign-in filter; correlate against subsequent New-InboxRule or MailItemsAccessed events (TL-2026-1810-SPL-002/KQL-002) within the same session to raise confidence before paging.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Employee Delivered M365-Branded Phishing Link From Lookalike Domain (locked: unlock with TL Creds)
- Mass MailItemsAccessed Burst From a Single Session (locked: unlock with TL Creds)
- Single Session/IP Enumerating Permissions Across Multiple Mailboxes (locked: unlock with TL Creds)
- AiTM Session-Cookie Reuse — Sign-In Without Fresh MFA Challenge (Sigma) (locked: unlock with TL Creds)
- Suspicious New Inbox Forwarding Rule After Sign-In (Sigma) (locked: unlock with TL Creds)
- Outbound Relay to Newly Registered Domain Following Mass Mail Access (locked: unlock with TL Creds)
- Malicious Inbox Forwarding/Redirect Rule Created by Non-Admin Mailbox (locked: unlock with TL Creds)
- OAuth Application Consent Grant to Unfamiliar Publisher With Mail Scopes (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Mon General Hospital notifies patients of phishing attack, potential data breach](https://www.wdtv.com/2026/07/31/mon-general-hospital-notifies-patients-phishing-attack-potential-data-breach/)
- [Mon General Hospital notifies patients of phishing attack and breach](https://databreaches.net/2026/08/01/mon-general-hospital-notifies-patients-of-phishing-attack-and-breach/)
- [Mon General hit by phishing attack; says patient information may have been leaked](https://www.wboy.com/news/monongalia/mon-general-hit-by-phishing-attack-says-hacker-may-have-patient-information/)
- [Mon General confirms systems hit by phishing attack; says patient information may have been leaked](https://wajr.com/2026/08/01/mon-general-confirms-systems-hit-by-phishing-attack-says-patient-information-may-have-been-leaked/)
- [Monongalia Health System Suffers Another Major Data Breach](https://www.hipaajournal.com/monongalia-health-system-suffers-another-major-data-breach/)
- [West Virginia-Based Monongalia Health System Suffers Phishing Attack](https://www.techtarget.com/healthtechsecurity/news/366594658/West-Virginia-Based-Monongalia-Health-System-Suffers-Phishing-Attack)
- [400,000 Individuals Affected by Email Breach at West Virginia Healthcare Company](https://www.securityweek.com/400000-individuals-affected-email-breach-west-virginia-healthcare-company/)
- [US HC3 warns BEC emerges as one of 'most financially damaging' cybersecurity threat to healthcare sector](https://industrialcyber.co/medical/us-hc3-warns-bec-emerges-as-one-of-most-financially-damaging-cybersecurity-threat-to-healthcare-sector/)
- [HC3 reveals credential harvesting threat targeting healthcare sector, provides mitigation strategies to reduce risk](https://industrialcyber.co/medical/hc3-reveals-credential-harvesting-threat-targeting-healthcare-sector-provides-mitigation-strategies-to-reduce-risk/)
- [Microsoft seizes 338 websites to disrupt rapidly growing 'RaccoonO365' phishing service](https://blogs.microsoft.com/on-the-issues/2025/09/16/microsoft-seizes-338-websites-to-disrupt-rapidly-growing-raccoono365-phishing-service/)
- [HHS HC3 Sector Alert: Business E-mail Compromise in Organizations](https://chscpr.org/hhs-hc3-sector-alert-business-e-mail-compromise-in-organizations/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1810
