BORIS for Autodesk Inventor - Secure Your CAD Designs

Clop PLM Data Leak: Stolen Engineering Drawings Online, What Inventor and Vault Teams Should Check | Autodesk Inventor | Register and Certify Ownership of CAD design

2026-10-18 15:30 News
On 8 October 2026 Dutch news radio BNR reported that the Clop extortion gang has published data it stole from Philips and Shell on the dark web. BNR reviewed the Philips files and found technical drawings of MRI scanners and other medical equipment. Security researchers link the theft to a critical flaw in PTC's Windchill and FlexPLM product data platforms, the systems where engineering teams keep their models and drawings.
The story started in August, when Clop began naming more than 40 organisations on its leak site and said it had taken engineering drawings, project plans and blueprints. Most of the companies said they were investigating, and none confirmed a significant breach at the time. The October report is the next step in a familiar extortion pattern: when victims do not pay, the data is put online for anyone to download.
Autodesk products are not part of this campaign. The flaw is in PTC software, and no Autodesk product is named in any of the reports. But Inventor teams run the same kind of system: an Autodesk Vault server that holds every part, assembly and drawing the company has ever made, often reachable by remote staff, suppliers and job processors. This article explains what happened, separates what is claimed from what is confirmed, and lists what Inventor CAD managers should check on their own Vault setup this week.
TL;DR: the Clop PLM leak in one paragraph

Clop exploited a critical flaw in internet-facing PTC Windchill and FlexPLM servers, most likely as a zero-day from early June 2026, and claims to have stolen data from more than 40 organisations, including Shell and Philips. PTC released patches from 17 June. On 8 October, BNR reported the stolen Philips and Shell data had been published, and that the Philips files include technical drawings of medical equipment. The lesson for Inventor teams: your Vault server is the single place an attacker can take your entire design history from. Keep it off the open internet, patch it, rotate its credentials, watch for bulk downloads, and keep independent proof that the designs are yours.

What did BNR find in the leaked data?

According to the BNR investigation, reported in English by NL Times, Clop published the stolen Philips and Shell data on its dark web site. BNR looked at the Philips files and sent several of them to Philips for verification. They included technical drawings of MRI scanners and other medical equipment, and information about Philips' IT infrastructure. BNR could not access the Shell data. You can read the NL Times report of 8 October for the full summary.
For Shell, Clop claims 89 GB, including construction drawings, facility photos, scans of test reports and project plans. For Philips, monitoring firm GalaxyWarden reported a claim of about 13.5 GB, including diagrams and blueprints, and stressed that the figures come from the hackers and were not independently verified. In August, Shell said it was "aware of a potential incident". Philips described an attempted cyberattack on a specific company server containing internal data, said the incident was under control, and added: "This has no impact on customer environments."

How did the attackers get to the drawings?

Security researchers, including Ransom-ISAC and ReliaQuest, tied the campaign to CVE-2026-12569, a critical vulnerability in PTC Windchill and FlexPLM. It lets a remote attacker run code on an exposed server without any credentials. Ransom-ISAC assesses that Clop used it as a zero-day from early June 2026, before a fix existed.
PTC began releasing patches on 17 June and warned of heightened threat activity on 26 June. The US cybersecurity agency CISA added the flaw to its Known Exploited Vulnerabilities catalogue in June and gave federal agencies three days to secure their systems, and Germany's BSI urged PTC customers to patch quickly. Clop started sending extortion emails around 20 July and began naming victims on its leak site from 12 August.
Once inside, the attackers installed web shells, small programs that give remote control of the server. ReliaQuest reported that the implant maps the file vault and decrypts the credentials stored in the Windchill keystore, which can open the way to other systems. SecurityWeek's coverage of the more than 40 named victims describes it as the first Windchill vulnerability confirmed exploited in the wild.

What is claimed and what is confirmed?

Extortion gangs exaggerate, and early reports mix claims with facts. This table keeps them apart, based on public reporting up to 18 October 2026.
ItemWhat Clop or researchers claimWhat is confirmed publicly
Entry pointResearchers link the campaign to CVE-2026-12569 in Windchill and FlexPLMPTC patches since 17 June 2026; flaw in CISA's exploited list since June
Number of victimsMore than 40 organisations named on Clop's leak site from 12 AugustNamed companies said they were investigating; GE was listed and later removed
Shell89 GB, including construction drawings, facility photos, test reports, project plansShell said it was aware of a potential incident; BNR could not access the data
PhilipsAbout 13.5 GB, including diagrams and blueprintsPhilips confirmed an attempted attack on one server; BNR saw MRI scanner drawings in the leak
Other named firmsFiserv, Zebra Technologies, Ingersoll Rand, Toast, Mindray, Largan Precision and othersNo significant breach confirmed by the companies in the reporting we reviewed
Autodesk productsNot named in any reportThe vulnerability is in PTC software only
The pattern matters more than the totals. Clop does not pick one company and study it. As one researcher put it, the gang targets a specific vulnerability and goes after everyone who runs it. That is why small manufacturers with one exposed server can end up on the same list as Shell.

Why should Inventor and Vault teams care?

Because a PDM server is the best target in a manufacturing company. Email holds fragments; the vault holds everything: native Inventor parts and assemblies, drawings, BOMs, revision history, and often supplier data. Steal it once and you have the whole product line. Our explainer on how often cyberattacks target manufacturing IP and the article on the costs of CAD data breaches show why criminals keep coming back to engineering data.
Autodesk Vault is a different product with a different code base, and nothing in this campaign suggests a Vault flaw. But the risk factors are the same ones that turned Windchill servers into victims: a server reachable from the internet so that remote staff or partners can log in, patches applied months late, powerful service accounts, and nobody watching for unusual downloads. Vault has its own security updates too, and Autodesk's advisory list moves fast, as our report on the ADP Desktop SDK advisory ADSK-SA-2026-0017 showed this week.
There is also a legal side. A leaked drawing is not just a lost file. Trade secret protection depends on showing you took reasonable steps to keep information secret, and a court will look at how the data was stored and who could reach it. Our analysis of the court ruling that treated complete 3D model files as trade secrets explains why the way you guard your models can decide a case.
Leaked files can be copied. Your proof of creation should not depend on them staying secret.

BORIS for Autodesk Inventor registers your CAD files with a blockchain timestamp and a certificate of ownership, directly inside Inventor.

👉 Discover BORIS for Autodesk Inventor

What should Inventor CAD managers check this week?

  1. Find out if your Vault server is reachable from the internet. Ask IT whether any port forward, public IP or reverse proxy points to the Vault or ADMS server. If remote users need access, use a VPN or a brokered option such as Autodesk Vault Gateway, which relays connections over HTTPS without opening inbound firewall ports.
  2. Patch Vault, ADMS and the job processor. Install the latest Vault update and hotfixes, and the Windows and SQL Server updates under them. Check Autodesk's security advisories monthly, not once a year.
  3. Rotate service and admin credentials. Change the Vault administrator password, SQL and service account passwords, and remove accounts of people who left. Clop's implant went straight for stored credentials.
  4. Review who can download what. Use Vault groups, roles and category-based security so suppliers and contractors see only their projects. Our guide to Inventor PDM security walks through the settings.
  5. Watch for bulk downloads and odd hours. Large get operations or exports at night are a warning sign. Our article on tracking who accesses your CAD files explains what to log.
  6. Keep independent proof of your key designs. Register important versions with a timestamp outside the vault, so a leak or a ransomware wipe does not take your evidence of authorship with it.
Remote work makes the first step the hardest. If your team works from home or from supplier sites, our remote CAD team security protocols and the Inventor Vault setup and management tips cover safe ways to give access without exposing the server.

What happens to a company after its drawings leak?

Once drawings are on a leak site, they cannot be recalled. Competitors, counterfeiters and other criminals can download them, and the company has to deal with customer questions, supplier contracts and possibly regulators. Our overview of the consequences of CAD file leaks covers the business impact, and CAD data security challenges in supply chains explains why partners' copies make the exposure bigger.
What a company can still control is evidence. If a copied design turns up in someone else's product, the question becomes: who created it first, and can you prove it? Vault history helps, but it lives on the same server that may have been compromised, and a vault database is something you control and could in theory edit. An independent, tamper-evident timestamp is stronger, as we explain in how to prove design ownership in legal disputes and in our look at the limits of digital vaults for CAD storage.

What is still unclear?

  • Whether all the leaked data is real. BNR saw Philips files and sent them for verification, but could not access Shell's data. Clop's size figures are its own claims.
  • The full victim list. More than 40 organisations were named, one was removed, and not every company has commented.
  • How many servers were hit. No complete count of compromised Windchill and FlexPLM systems has been published.
  • Whether other PLM and PDM products will be targeted next. Nothing has been reported for Autodesk Vault. Clop's history shows it moves from one file-handling platform to the next, so treat every exposed engineering server as a candidate.

The bigger picture across the BORIS network

This week's news on our sister sites points the same way: attackers and automated tools are going after engineering data, and access rules decide how much they get.
CADChain explains how its CAD data protection technology works across tools, and our guide on protecting trade secrets in manufacturing covers the Inventor side.

Conclusion

The Clop campaign did not need stolen passwords or a clever phishing email. It needed one critical flaw in a product data server that was reachable from the internet, and it ended with engineering drawings on the dark web. Autodesk Vault is not affected by this flaw, but Inventor teams run servers with the same value and often the same exposure. Check whether your vault can be reached from outside, patch it, rotate its credentials, limit and log downloads, and keep proof of your designs that does not live on the server an attacker would empty first.
Your designs, your proof.

BORIS for Autodesk Inventor gives every registered file a blockchain timestamp and a certificate of ownership, without sending your models to a cloud service.

👉 See how BORIS for Autodesk Inventor works

FAQ: the Clop PLM data leak and Inventor teams

What happened on 8 October 2026?

BNR reported that the Clop gang had published data stolen from Philips and Shell on the dark web. BNR reviewed the Philips files, which included technical drawings of MRI scanners and other medical equipment, and could not access the Shell data.

Which software was exploited?

Security researchers link the campaign to CVE-2026-12569, a critical flaw in PTC Windchill and FlexPLM that allows remote code execution without credentials. PTC released patches from 17 June 2026.

Is Autodesk Vault affected?

No Autodesk product is named in any report, and the vulnerability is in PTC software. Vault teams should still check internet exposure, patch levels and credentials, because the same kinds of weaknesses made the Windchill servers easy targets.

Were Shell and Philips confirmed as breached?

Philips confirmed an attempted attack on a specific server containing internal data and said customer environments were not affected. Shell said it was aware of a potential incident. Clop's data volumes are its own claims.

How many organisations were hit?

Clop named more than 40 organisations on its leak site from 12 August 2026, including Shell, Philips, Fiserv, Zebra Technologies, Ingersoll Rand, Toast, Mindray and Largan Precision. GE was listed and later removed.

Should our Vault server be on the internet?

Not directly. Give remote users access through a VPN or a brokered option such as Autodesk Vault Gateway, keep the server patched, and limit and log what each group can download.

What can we do if our drawings have already leaked?

Contain the incident with IT and legal advice, tell affected partners as your contracts require, and gather evidence of when and by whom the designs were created. Independent timestamps made before the leak are the strongest evidence.

How does BORIS help?

BORIS for Autodesk Inventor registers CAD files with a blockchain timestamp from inside Inventor. Each registered version gets a dated certificate of ownership that is stored outside your vault, so a leak or a server wipe does not erase your proof of authorship.