Philips compromised in Clop ransomware attack
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Clop ransomware operators claim compromise of Philips with 413 employee credentials and 60k user accounts exposed.
Ransomware.live, a public tracking platform that indexes ransomware operator claims, reports that Clop ransomware operators have posted Philips (philips.com) as a victim. According to the posting, the compromise involved 413 compromised employee accounts, 60,802 compromised user accounts, and 793 third-party employee credentials. The attackers also identified 200 external attack surface items and obtained DNS records for the victim's domain. This appears to be data exfiltration prior to encryption, consistent with Clop's typical double-extortion model. The posting includes a leak screenshot as evidence, though the underlying stolen data is not hosted on the tracking platform itself.
Defenders should treat this as a confirmed intrusion into a major multinational technology vendor. Philips operates critical infrastructure software and medical devices used across healthcare and enterprise environments. The scale of credential compromise (413 employees plus 60k additional users) suggests either broad network access or compromise of authentication systems. The external attack surface discovery indicates reconnaissance of internet-facing assets.
Mentioned in this report
Detection guidance
2 detections for this report are in the app — rules that match its indicators, converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, plus YARA and Suricata. Three days of it free, no card.
Source reporting: https://www.ransomware.live/id/UEhJTElQUy5DT01AY2xvcA==
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs