tl;dr
- Cl0p has named 43 organisations, including Shell, Philips, Fiserv and, briefly, GE, claiming it stole their data, and researchers blame it for exploiting CVE-2026-12569 in PTC Windchill and FlexPLM servers, probably from early June, before PTC disclosed the flaw on 17 June.
- Fewer than 100 of these servers were exposed to the internet, and a custom web shell (a script planted on a web server to take an attacker’s commands) found on them ran inside Windchill itself, decrypting its stored passwords and mapping the vault that holds the CAD files.
- Philips, Toast, Zebra and Shell acknowledge some access, but as of 21 August none has said how, or that Windchill was the way in.
An email about a data leak, from a compromised account
On 20 July 2026, hundreds of staff at manufacturers and engineering firms received an email with the subject line “Windchill PDMLink module serious data leak”. Ransom-ISAC, a ransomware information-sharing group that began seeing the emails that day, says they appear to come from randomly compromised accounts and go to hundreds of people in each organisation. They give the newest contact addresses of Cl0p, a ransomware and extortion group, on two domains that Censys, an internet-scanning company, found were registered three days earlier. By then the senders had probably been inside those companies’ engineering systems for about six weeks.
Windchill is PTC’s product lifecycle management (PLM) software, where a manufacturer keeps the master record of what it makes: CAD models and drawings, the bill of materials (the full parts list), and every change since the first sketch. PDMLink is the module that manages that data; FlexPLM is the variant PTC sells to retail and apparel brands. Apache sits in front and only forwards requests. The application runs in a Java process PTC calls the Method Server, with its own Tomcat web container built in, and that detail decides what defenders can see.
Cl0p’s best-known mass thefts went after file-transfer appliances, where the loot was whatever customers happened to send through them, much of it personal data. ZeroFox, a threat intelligence vendor, calls Windchill a shift to intellectual property. This time, if ReliaQuest, a security vendor, is right to call the attribution “highly likely”, Cl0p went for the system that holds the blueprints.
PTC disclosed the flaw, CVE-2026-12569, on 17 June and shipped patches between 18 June and 14 July; CISA added it to its Known Exploited Vulnerabilities catalogue on 25 June. The emails began on 20 July, and from 12 August Cl0p’s leak site showed full victim names (Security Affairs).
Eleven posts, and the numbers drift
Between 1 and 21 August, Obstracts collected 11 posts about the campaign from nine sources, all of them from 14 August onwards, once Shell and Philips appeared on the leak site. Most rewrite each other, and the headline number drifts: ThreatCluster puts it at nearly 50 companies, Security Affairs says “40+”, and the leak-site batch ZeroFox counted has 43.
Only one of the 11, ReliaQuest’s, is a primary report. The rest of the first-hand evidence comes from outside those 11:
| Source | What it saw | What it lacks |
|---|---|---|
| PTC’s advisory (17 June to 20 August) | The vendor: the flaw, patches, workarounds, indicators and hunting guidance | Any actor, any victim count, how PTC learned of the flaw |
| Ransom-ISAC (22 July, updated to 19 August) | With eCrime.ch and DEFUSED: the first attribution, the exploit chain, a C2 address from an active incident, a YARA rule | Victims |
| ReliaQuest (18 August) | The custom web shell’s commands and the case for Cl0p, cited here via BleepingComputer and The Hacker News because the live page was revised after 21 August | Where the shell was found |
| Censys (30 July) | Exposed servers and a timeline of attacker infrastructure | Which servers were compromised |
| Securonix (19 August) | A SIEM vendor: how Windchill is built, why the custom shell is hard to see, a detection for each shell | Indicators or victims |
| ZeroFox (21 August) | 43 names posted between 14 and 19 August, claimed volumes, GE’s removal | Confirmation from any victim |
| Victims’ statements, via BleepingComputer, ISMG, eSecurity Planet and CyberScoop | What Shell, Philips, GE, Fiserv, Toast and Zebra say | How any of them was breached |
They agree on the flaw, the folder the web shells were dropped into and the leak site, and differ on details that matter when you hunt. ReliaQuest said on X in July, as The Hacker News reported, that the actor “remains unconfirmed”, and in August called it “highly likely” Cl0p.
Who is blamed, and on what evidence
In this case Cl0p blames itself: the names are on its leak site and the emails ask victims to get in touch. Researchers go less far, and PTC’s advisory never names an actor. Ransom-ISAC lists the group’s other names as Graceful Spider, Chubby Scorpius, FIN11 and Lace Tempest.
Ransom-ISAC published first, on 22 July, and attributes the activity to “alleged” Cl0p affiliates. ReliaQuest’s 18 August analysis calls the attribution “highly likely”, for three reasons:
- the extortion emails give contact addresses that also appear on Cl0p’s leak site;
- the web shell uses
X-windchill-reqcommand headers seen in earlier intrusions; - the tactics match Cl0p’s earlier campaigns.
The third reason is the most telling. Cl0p writes a web shell for each product it exploits: DEWMODE for Accellion’s File Transfer Appliance (CVE-2021-27101) and LEMURLOOT for Progress MOVEit Transfer (CVE-2023-34362), and ReliaQuest puts the Windchill implant in the same line. Find a flaw in a product that holds valuable data, write a tool that speaks its language, steal from every exposed install at once, then extort in bulk.
43 names, four admissions
ZeroFox counted 43 organisations posted to the leak site between 14 and 19 August. Those are Cl0p’s claims. The companies named in coverage tell a smaller story:
| Company | Cl0p claims | What the company says |
|---|---|---|
| Shell | 89 GB | On 14 August, “We are aware of a potential incident.” Later, unauthorised access to “a cloud-based IT service, managed by a third party”, used for non-critical operations, now blocked, with no operational impact |
| Philips | 13.5 GB | It “identified and contained an attempted cybersecurity compromise of a specific enterprise server”, with “no impact on customer environments” |
| GE | 391 GB | “Working to assess the potential issue”; gone from the leak site by 17 August |
| Fiserv | 874 GB, including CAD files | No customer, bank, transaction or personal data stolen |
| Toast | Not given | “Unauthorized access to a limited number of files”, nonsensitive internal documents, contained |
| Zebra | Not given | “Detected and contained system intrusions”, with what it calls limited impact (CyberScoop) |
| Ingersoll Rand, Mindray, Largan | Not given | No public statement by 21 August |
None of the four says how, or ties it to Windchill. Fiserv’s denial says nothing about the CAD files Cl0p claims.
Shell’s account points away from Windchill: a cloud service run by a third party doesn’t sound like an on-premises server, and Shell hasn’t named it.
How the break-in worked
The companies won’t say how, but the servers do. PTC, Ransom-ISAC, ReliaQuest and Securonix each describe part of what happened to an exposed Windchill server, and in order it runs in eleven steps. If Attack Flows are new to you, Beyond the ATT&CK Matrix: How to Build Dynamic Attack Flows with STIX explains how to read one.
- Fingerprint the server without logging in (Vulnerability Scanning, T1595.002). Ransom-ISAC describes a
GETto/Windchill/rfa/jsp/login/*.jsp?wsdl, which on FlexPLM returns the WSDL (the machine-readable description of a web service) to anyone; a 4,045-byte response confirms the target. This information leak has no CVE of its own, and PTC’s hunting guidance looks for the same probe. - Exploit CVE-2026-12569 (Exploit Public-Facing Application, T1190). The flaw is deserialisation of untrusted data in the login servlet: Windchill turns bytes from the request back into Java objects, and the right bytes run code, no account needed. PTC’s workaround, a Java serialisation filter for
com.ptc.wpcfg.logic.ExpressionClassMethodthat it updated on 29 June, shows which class it was worried about. - Drop a web shell into the login folder (Web Shell, T1505.003). JSPs (JavaServer Pages) are pages Tomcat compiles and runs on request. The custom shell lands in
/Windchill/login/with a filename of 16 hex characters. - Send commands in an HTTP header (Web Protocols, T1071.001). The operator puts a single command letter in an
X-windchill-reqheader, and the shell gzips its replies. One command,E, echoes back a second header,X-windchill-prm. - Decrypt Windchill’s stored secrets (Credentials In Files, T1552.001). The
Scommand readsieStructProperties.txtand the keystore and decrypts the LDAP manager password, the account Windchill uses to query the corporate directory. - Map the vault (File and Directory Discovery, T1083). The
Lcommand queries the vault tablesApplicationData,FVITEM,FVMOUNTandMasteredOnReplicaItemand writes the result toflst.txt: a map of where every stored file sits on disk. TheOcommand reports the operating system (System Information Discovery, T1082). - Load more code in memory (Reflective Code Loading, T1620). The
Jcommand takes Base64-encoded ZIPs of Java bytecode and loads them through a class loader calledCldr, without writing them to disk. - Collect the engineering data (Data from Information Repositories, T1213): CAD files and documents from the vault.
- Send it out through the shell (Exfiltration Over C2 Channel, T1041). PTC suggests alerting on multi-megabyte responses to POSTs to JSPs, which is what this looks like on the wire.
- Delete files (File Deletion, T1070.004) with the
Rcommand. - Extort (Financial Theft, T1657): the emails from compromised accounts beginning 20 July, and the leak site from 12 August.
Steps 5 to 10 are commands the shell supports in ReliaQuest’s analysis, rather than a sequence any victim has published. Their order is a reading of what an operator needs first: passwords and a map before the data.
A web shell that borrows Windchill’s identity
Most web shells give themselves away by starting processes. Send ?cmd=whoami and the web server spawns whoami, and an EDR (endpoint detection and response) product flags that process tree. The second shell family on these servers works like that: six-hex-character names, commands in a ?cmd= parameter, Java’s Runtime.exec, and whoami and id as child processes in Securonix’s analysis. PTC added its filename pattern on 8 July. No source attributes it to Cl0p’s operators; PTC and Ransom-ISAC list it only as an indicator of the same exploitation, so it isn’t in the steps above. A third family, named dpr plus hex characters, is on the same lists with the same caveat.
The custom shell spawns nothing. Because Windchill’s Tomcat runs inside the Method Server’s Java process (wt.method.MethodServerMain), a JSP in the login folder loads into the same JVM (Java virtual machine) as the application, with Windchill’s own classes in reach. The shell uses them: MethodContext, the database connection WTConnection, and the keystore utility WTKeyStoreUtil. It doesn’t need to escalate privileges, because it already runs as the account Windchill was installed under.
It lives off the application rather than the land: process telemetry sees a healthy Method Server, Apache’s default access log drops the command header, and the web tier sees only a POST to a JSP, the one thing the shell can’t hide.
What nobody has confirmed
Five questions were still open on 21 August.
When it started. Ransom-ISAC “suspects” a zero-day. Censys saw rapid service churn on the indicator addresses in early to mid June, with dated changes on 4 and 11 June, ahead of PTC’s 17 June disclosure. PTC hasn’t said how it learned of the flaw, when exploitation began or how many customers were hit, as CyberScoop points out. The earliest web shell timestamp from any victim would settle it.
Whether the noisy shells are Cl0p’s. PTC lists the other families without naming anyone, and Securonix leaves the dpr family’s origin unconfirmed. Infrastructure shared with the custom shell, or both kinds of shell on one server in the same intrusion, would answer it.
Whether any named victim came in through Windchill. None has said so. Only a victim’s own disclosure, in a regulatory filing or a breach notice, can show it.
The exploit chain. Ransom-ISAC and The Hacker News describe the FlexPLM WSDL leak chained with the login-servlet flaw. PTC’s hunting guidance includes the same WSDL probe, which it says “precedes webshell deployment”, but doesn’t say how one leads to the other. On 20 August PTC disclosed two more flaws, CVE-2026-77645 and CVE-2026-77646, without saying whether they have anything to do with it.
What comes next. By 21 August no source had documented ransomware deployed on any network, a second stage beyond the web shell, or any stolen data published. The leak site has names and claimed volumes, nothing more.
What defenders can hunt for
The attack surface is small enough to check by hand. Censys counted fewer than 100 Windchill and FlexPLM servers exposed to the internet on 1 June, about 80% of them in the US and about a quarter behind Akamai, and a little over 80 on 20 July, by a later Censys count The Hacker News reported. If yours is one, six addresses, two domains, two filenames and two hashes are in the reference section. Four of the addresses come with the clearest history:
5[.]180[.]41[.]35: a command-and-control address in PTC’s hunting guidance.216[.]152[.]148[.]54: added to PTC’s indicators on 23 June.79[.]141[.]160[.]78: added by Ransom-ISAC on 14 August, observed “during an active incident”.78[.]128[.]113[.]10: in PTC’s indicators since 1 July. Censys, checking PTC’s addresses, found SSH on it from 23 April and, as of 17 July, tooling for Platypus, an open-source tool for managing reverse shells. Platypus isn’t known Cl0p tooling, so that part may be unrelated even though the address belongs on the list.
The extortion domains, cryptohox[.]com and cypherhex[.]com, registered on 17 July through the registrar CNOBIN, show up in mail, not on the Windchill server. On the server, look for a JSP with a 16-hex-character name under <WT_HOME>/codebase/login/ (<WT_HOME> is the Windchill install directory), and for flst.txt, which PTC says to look for in /tmp or the Windchill working directory.
The file indicators are worth a sweep on every Windchill server, exposed or not. The dpr pattern accepts six to eight characters because PTC’s text says eight and its own search pattern matches six. The commands need GNU find:
# JSPs with 16- or 6-hex-character names, or dpr names, in the login folder
find "${WT_HOME:?set WT_HOME}/codebase/login" -type f -regextype posix-extended \
\( -regex '.*/[0-9a-fA-F]{16}\.jsp' \
-o -regex '.*/[0-9a-fA-F]{6}\.jsp' \
-o -regex '.*/dpr_?[0-9a-fA-F]{6,8}\.jsp' \)
# The custom shell's vault map (PTC: /tmp or the Windchill working directory)
find "${WT_HOME:?set WT_HOME}" /tmp -type f -name 'flst.txt'
PTC publishes its own filename patterns and Ransom-ISAC a YARA rule, JSP_Webshell_Windchill_Structural, for matching shells by content rather than name.
A rule for the login folder
Filenames and addresses change with the next build. PTC’s hunting guidance has one observation that won’t: legitimate traffic does not POST to JSPs in /Windchill/login/. The same guidance says to block the X-windchill-req header and to alert on multi-megabyte responses to those POSTs, which puts the custom shell’s commands and its stolen data in that kind of request.
If you are new to Sigma, Writing Effective Sigma Detection Rules: A Guide for Novice Detection Engineers explains each field. This one is for the Apache or reverse-proxy logs in front of Windchill:
title: POST Request to a JSP in the Windchill Login Folder
id: 7863677f-9708-54aa-9f1d-d59b774524ce
status: experimental
description: Detects HTTP POST requests to JSP files under /Windchill/login/ on PTC Windchill or FlexPLM. PTC says legitimate traffic does not POST to these files. In the 2026 exploitation of CVE-2026-12569, web shells were dropped in this folder, and the custom implant took its commands in POST requests and returned stolen data in the responses.
references:
- https://www.ptc.com/en/about/trust-center/advisory-center/active-advisories/windchill-flexplm-rce-vulnerability
- https://reliaquest.com/blog/clop-returns-with-custom-implant-in-mass-extortion-campaign/
- https://connect.securonix.com/threat-research-intelligence-62/two-web-shells-two-detections-instrumenting-ptc-windchill-against-clop-499
author: dogesec
date: 2026-08-21
tags:
- attack.command-and-control
- attack.t1071.001
- attack.exfiltration
- attack.t1041
logsource:
category: webserver
detection:
selection:
cs-method: 'POST'
cs-uri-stem|startswith: '/Windchill/login/'
cs-uri-stem|endswith: '.jsp'
condition: selection
falsepositives:
- An administrator or PTC support deploying and testing a JSP in the login folder during patching; check the file against the install's own file list
- Internal vulnerability scanners that POST to every JSP they find; exclude their source addresses
level: high
Two additions make it sharper: add %{X-windchill-req}i to Apache’s LogFormat, so any value in that field is a confirmed hit, and add a condition on response size (sc-bytes, if your logs carry it) of a few megabytes to separate the theft from the probing. The rule misses the noisy shells’ ?cmd= requests if they arrive as GETs; a process-creation rule for whoami or id under the Method Server, as Securonix suggests, catches those, and is exactly the rule the custom shell was built to beat. With only encrypted traffic and no web server logs, the rule sees nothing.
The rule sees steps 4 and 9, the commands going in and the data coming out. Everything between them (the decrypted passwords, the vault map and the code loaded in memory) happens inside the JVM, where nothing in a standard log can follow.
The whole case in one graph
Put together, this is the whole case: the six primary reports, Cl0p and the evidence against it, the flaw, the custom shell, the eleven steps, the indicators, the victims’ claims and denials, and the rule.
A hunter can start from any indicator or the rule and walk to the step it sees and the evidence behind it. An analyst can follow the attribution from Cl0p’s leak site to each report that supports it, and see that no victim is tied to Windchill.
In summary
If ReliaQuest is right, Cl0p ran its usual play against a new kind of target: a web shell written for one product, theft from every exposed install, then extortion in bulk, this time for engineering data. On 21 August the case stands at 43 claims, a “highly likely” from ReliaQuest, silence on attribution from PTC, four partial admissions and no confirmed way in. For hunters, the signal that survives the next build is in PTC’s guidance: nothing legitimate POSTs to a JSP in the login folder, so log those requests, log the X-windchill-req header, and alert on both.
Reference: IoCs and ATT&CK techniques
For copying into tools that don’t use STIX. Each row gives the STIX ID of the matching object in the graphs above.
IoCs
| Type | Value | What it is | Linked to | Confidence | STIX ID |
|---|---|---|---|---|---|
| IPv4 | 5[.]180[.]41[.]35 |
C2 address in PTC’s hunting guidance; one of Ransom-ISAC’s four new C2 indicators on 22 July 2026 | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--cc52c551-d6b4-576e-95c4-a30aa7f2e22a |
| IPv4 | 216[.]152[.]148[.]54 |
Added to PTC’s indicators on 23 June 2026; one of Ransom-ISAC’s four new C2 indicators on 22 July 2026 | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--8933ecf4-8d7f-5883-a04d-224a7055f8df |
| IPv4 | 216[.]152[.]151[.]204 |
In PTC’s indicators from 9 July 2026; one of Ransom-ISAC’s four new C2 indicators on 22 July 2026 | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--2a34c78e-2f08-5e8f-a6a0-bef8bf6e22cf |
| IPv4 | 104[.]243[.]35[.]63 |
One of Ransom-ISAC’s four new C2 indicators on 22 July 2026 | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--d71cdc5c-493f-55d1-b64d-591501af7f7a |
| IPv4 | 79[.]141[.]160[.]78 |
C2 observed “during an active incident” (Ransom-ISAC, 14 August 2026) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--cd056b64-7e8f-5705-8008-0b644adfa7ad |
| IPv4 | 78[.]128[.]113[.]10 |
In PTC’s indicators from 1 July 2026; Censys saw Platypus C2 tooling on it as of 17 July | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--2069b86c-3d5b-5a03-a97b-57a00c1c44b7 |
| Domain | cryptohox[.]com |
Extortion contact domain, registered 17 July 2026 (Censys) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--2f3edc97-b630-5b22-9487-ceb38f7880ce |
| Domain | cypherhex[.]com |
Extortion contact domain, registered 17 July 2026 (Censys) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--973a31eb-1ebb-5a3d-bda9-8a3206e7329c |
| File | JSP with a 16-hex-character name in <WT_HOME>/codebase/login/ |
The custom web shell (PTC, Ransom-ISAC) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--6add0fdb-f27f-52b2-a801-28d914e646b5 |
| File | flst.txt |
Vault map written by the custom web shell (PTC, Ransom-ISAC) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--086243ba-9d96-592c-8700-89a04b5af5a6 |
| SHA-256 | 55a1eb4c2d3da04376df39d7ba832569c6af1a37a0cf2b95f754ac898023a30c |
JSP under <WT_HOME>/codebase/login/ (PTC) |
Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--cb742c70-76e8-5ad8-80a1-a866db97685d |
| SHA-256 | 321e1fb01eb3462b48ff6ccdef132acc1182e3f7456548439f0d4ead12fd98bf |
Web shell sample from an active incident, matching ReliaQuest’s custom implant (Ransom-ISAC) | Windchill and FlexPLM exploitation and extortion, 2026 | High | indicator--3bf4b35b-782a-59f5-aa65-a3e9ef2a864a |
Techniques
| Step | Action | Technique | Tactic | STIX ID |
|---|---|---|---|---|
| 1 | FlexPLM servers fingerprinted through the WSDL leak | T1595.002 | TA0043 | attack-action--7de6d336-dbf3-5283-b77e-3389a5aec721 |
| 2 | CVE-2026-12569 exploited in the login servlet | T1190 | TA0001 | attack-action--29097aff-6858-5a90-8108-2bdcc6232acf |
| 3 | JSP web shell dropped in /Windchill/login/ | T1505.003 | TA0003 | attack-action--9890ee5d-88e9-5001-9ce0-486eb9d84b25 |
| 4 | Commands sent in the X-windchill-req header | T1071.001 | TA0011 | attack-action--3e3a5dd7-599f-59e6-a93b-3cb91507a989 |
| 5 | LDAP manager password and keystore decrypted | T1552.001 | TA0006 | attack-action--bbb43500-2a39-5acc-a457-00b79fce5e87 |
| 6 | File vault mapped to flst.txt (OS discovery, T1082, in the step’s description) | T1083 | TA0007 | attack-action--6e59429e-6695-5357-9ecc-f248f851886b |
| 7 | Java bytecode loaded in memory | T1620 | TA0005 | attack-action--0cd21df5-e3e0-56b2-82a6-1d61cca5bfdd |
| 8 | Engineering data collected from the vault | T1213 | TA0009 | attack-action--2f30623c-1c57-502d-8bed-0c8a35eb7d90 |
| 9 | Data sent out through the web shell | T1041 | TA0010 | attack-action--67ba3084-d703-5079-aee7-c74d00a2d9e2 |
| 10 | Files deleted | T1070.004 | TA0005 | attack-action--5c9eca83-4e8c-5fcf-84e6-375c437b5ec2 |
| 11 | Extortion emails and leak-site naming | T1657 | TA0040 | attack-action--5b8439db-7931-5f1b-b4b3-696f08aa4b74 |
The Sigma rule is indicator--7863677f-9708-54aa-9f1d-d59b774524ce, and the campaign is campaign--16ea7d06-21dd-5a22-97c6-86e30cd041a8.
Get new posts by email
New threat research and tutorials from dogesec, plus the weekly Obstracts threat brief. No spam, unsubscribe any time.
