What do hackers already know about your business? Get Your Free Report
Alleged

Penang Adventist Hospital Data Breach

Published: Nov 15, 2026 LockBit5

Threat Level

High

Confidence: High

Quick Summary

Company
Penang Adventist Hospital Data Breach
Industry
Healthcare
Threat Actor
LockBit5
Date of Incident
Nov 15, 2026

Executive Summary

Penang Adventist Hospital, a not-for-profit private hospital in Penang, Malaysia, was listed as a victim on lockbit5’s dark web portal on November 15, 2026. The listing was identified through SOCRadar’s Dark Web Monitoring service. The hospital provides surgery, emergency care, and specialist outpatient clinics, and operates in the Healthcare sector, which appears among lockbit5’s most frequently claimed victim categories. This alignment with the group’s observed sector preferences lends the listing operational context, although the claim remains an alleged breach pending independent confirmation. Over the 60 days preceding this listing, lockbit5 claimed 36 victims, with Healthcare, Professional Services, and Other sectors appearing most frequently in its victim set. The group’s activity is geographically concentrated in the United States, Brazil, and Italy. Recent lockbit5 listings that overlap with Penang Adventist Hospital’s profile — Malaysian organizations or Healthcare sector targets — include Sun Clinical Laboratories, STARMARK, PT Centratama Telekomunikasi Indonesia, and PT Synergy Risk Management Consultants. The hospital matches the group’s typical sector targeting through its Healthcare profile, while its Malaysian location falls outside the countries where lockbit5’s victim activity is most concentrated.

Technical Analysis

SOCRadar’s stealer-log telemetry surfaced six records for pah[.]com.my, all classified as INTERNAL_AUTH_EMPLOYEE. Each record shows a @pah[.]com.my corporate email address authenticating against SSO infrastructure at sso.emc[.]com — the precise credential profile ransomware operators use to validate access before deploying payloads. The dominant risk classification for this exposure is Corporate Intrusion Risk. No explicit freshness window was provided for all six records, but their presence in the queried sample indicates active credential exposure at the time of analysis. The observed pattern is consistent with the lockbit5 kill chain: infostealer operators harvest credentials, access brokers validate them against identity providers, and operators use SSO access to move laterally before encrypting systems. The stealer-log evidence does not confirm that these specific credentials were used by lockbit5, and no such attribution should be assumed. The records demonstrate exposed corporate authentication material at a listed ransomware target rather than a confirmed intrusion path, and the connection between the credential exposure and any actual compromise remains an unproven scenario. Nevertheless, exposed SSO credentials at an organization named on an active ransomware leak site warrant immediate response regardless of attribution. The exposed credentials should be rotated without delay, and authentication and access logs on the hospital’s SSO infrastructure should be reviewed for signs of unauthorized use. Continued monitoring of stealer-log feeds and dark web sources for additional records tied to the hospital’s domain will help determine whether the exposure widens or the listing develops into a confirmed data publication.

Disclaimer

This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.