CADChain Blog

ARTEX AI and Manufacturing: How AI Hacking Agents Reach OEM Design Data Through Weaker Suppliers | CADChain | CAD DRM & IP

News
TL;DR: What does ARTEX AI mean for manufacturing and engineering firms?

On 13 November 2026 the FBI warned that criminals use ARTEX, an open-source AI hacking framework, against manufacturing, semiconductor, defense and energy companies, among other sectors. Its agents go after side doors such as partner and supplier portals, map which companies trust each other and pivot from a weaker supplier into the bigger customer's network, some of them reaching privileged access in under three hours. For engineering firms the fix starts with access: list who connects to your CAD, PLM and file shares, close what has ended and keep design vaults off the open internet.
For the full news story, read what happened with ARTEX AI after the FBI warning; this guide stays with ARTEX AI and manufacturing and the design data that suppliers, OEMs and design studios hold. We covered the first espionage campaigns with ARTEX in our report on AI cyber espionage on 3 November; the new reports point straight at the supply chain.

Why does ARTEX AI put manufacturing firms at risk?

The FBI FLASH alert of 13 November 2026 says malicious actors have used ARTEX since at least August 2026 against organisations in financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications and legal work. Three findings matter most for product makers:
  • Speed. Some intrusions went from first targeting to privileged access in under three hours, as TechCrunch reported on 16 November.
  • Low skill. The FBI says the framework lets "threat actors with minimal technical expertise" run complex campaigns against several targets at once.
  • Supply chains. One supplier compromise, at ConnectWise Cloud Backup, gave access to more than 2,250 downstream tenants.

Which systems does ARTEX go after first?

The FBI says ARTEX "excels at identifying and exploiting peripheral systems receiving less security attention than flagship applications." Its list includes partner and supplier portals, employee apps, legacy services and third-party connections. In an engineering firm that means the portal where drawings go out for quotes, the old FTP server for CAM files and the PLM web client opened to a contract manufacturer. The Loxone attack on partner data and the latest Windchill vulnerability show how close these systems sit to the crown jewels.

How does an AI agent move from a supplier to an OEM?

The FBI writes that "autonomous agents can systematically map trust relationships between organizations". They look for a weaker third-party vendor, a CI/CD pipeline or a software provider, break in there and then "pivot from a peripheral supplier directly into high-value upstream enterprise networks." For an OEM (original equipment manufacturer), the weaker link is one of its own suppliers. If you supply an OEM, that weaker link can be you.
Way in seen by investigatorsIn an engineering firmFirst check
Vendor credentials used through B2B federation (FBI)A supplier's staff log in to your portal with their own company accountsWhich partner companies can sign in, and who approved them
Cross-account cloud trust from a partner tenant (FBI)A contract manufacturer's cloud account can read your storage bucket of drawingsEvery outside account with rights in your cloud
An access key given to a vendor and never retired (Barracuda)An integrator still holds a key from a PLM project that ended last yearKeys and accounts older than the contract behind them
Inside, the FBI saw the agents list more than 110,000 Active Directory objects, read local admin passwords, check which Windows machines had no endpoint sensor and create 100GB volumes to prepare data for exfiltration. Our guide to CAD file security in supply chain collaboration covers the file-sharing side of the same problem.

What did the Barracuda intrusion show?

On 11 November Barracuda published its own case. The attacker used a valid cloud access key that Barracuda had given a third-party AI vendor for an earlier project and never retired; Barracuda's verdict was "That is on us." In about 44 hours the attacker touched about 10 cloud accounts, read secret stores and pushed code branches that started a build which printed secrets into the logs. Barracuda's CISO Arve Kjoelen, quoted by TechCrunch: "Defenders who rely on spotting malicious activity and then responding to it will often arrive after the attacker has finished." The lesson for engineering firms: access that nobody remembers is the access an agent finds.

Who connects to your CAD, PLM and file shares?

Start with a supplier and partner access review. Fill in this table with your IT provider:
Who connectsHowLast reviewedAction
Machining or tooling supplierPortal login, shared drawings mailboxFill in the dateNamed accounts only, end date set to the contract end
Contract manufacturerPLM web client, cloud storage shareFill in the dateRead access to their parts only, sign-in via your identity provider
Design studio or freelancerShared folder, SFTP accountFill in the dateClose when the project ends
CAD/PLM integratorAdmin account, API key, remote support toolFill in the dateRotate keys, limit sign-in to known networks
Software and backup providersApp permissions in your cloud tenantFill in the dateList granted rights, remove unused apps
Any row with an unknown date or a shared login is your first job. The FBI asks companies to inventory all internet-facing applications, peripheral systems included.

How do you keep design data away from the internet?

The FBI recommends moving enterprise applications behind Zero Trust access and limiting admin and backup platforms to trusted networks. Cloudflare's guidance of 13 November adds identity-gated access for high-risk apps, micro-segmentation, rate limits and hardware security keys. For design data the rule is simple: a supplier who needs one assembly sees that assembly, and the vault stays out of reach. Our piece on zero trust for CAD file distribution shows how this works for shared files.

Where do secrets hide in engineering teams?

The FBI tells companies to scan repositories, build artifacts and pipelines for exposed secrets and rotate them promptly. In engineering teams, check PLM sync scripts, CAM post-processor folders, firmware build servers and test rigs. Cloudflare found attackers taking static, non-expiring CI/CD tokens again and again, and Amazon's threat intelligence team says agents succeeded where default passwords, keys in code and unpatched software were left in place.

What should you log, keep and report?

  • Save sign-in and audit logs from your identity provider, cloud and PLM before you change anything.
  • Alert on sequential lookups and unusually high record counts on partner and employee portals.
  • Don't delete a suspicious app first; the FBI asks you to preserve its settings and evidence.
  • Report suspected ARTEX activity to your FBI field office or ic3.gov, or your national cyber agency.

What should you ask your CAD/PLM vendor and IT provider?

  • Which of our systems can be reached from the internet today, and which of them hold design data?
  • Which outside accounts, apps and keys have access, and when does each one expire?
  • Do you scan our scripts, pipelines and backups for stored secrets?
  • Which machines run no endpoint sensor, and how fast would you see bulk downloads from the vault?

What should suppliers tell their OEM customers?

If you supply an OEM, your access is part of their attack surface. Tell your customers which of their systems you connect to, confirm you have reviewed those accounts, and agree who calls whom if either side sees strange activity. Ask them to remove accounts your team no longer uses. Check your contracts for any notice duties they already contain, and follow those.

What should engineering firms do this week?

  1. Fill in the access table for CAD, PLM and file shares.
  2. Close accounts and keys from finished contracts.
  3. Put vaults, PLM admin pages and backup consoles behind identity-gated access.
  4. Scan repositories, pipelines and scripts for secrets and rotate what you find.
  5. Store sign-in and download logs where an attacker can't wipe them.
  6. Check that every Windows machine opening design files runs your endpoint sensor.
  7. Send the questions above to your vendors, and agree a contact plan with each OEM.
Access control decides who reaches a file. CADChain registers and protects the CAD files themselves, so you can still prove you own a design after a copy leaves through a supplier's share.

FAQ: ARTEX AI and manufacturing

What is ARTEX AI?

ARTEX is an open-source AI penetration testing framework written in Go. Its AI agents turn a plain-language goal into attack commands, using outside models such as DeepSeek, Claude or GPT. Criminals have used it since at least August 2026.

Is the manufacturing industry targeted by ARTEX?

Yes. The FBI FLASH alert of 13 November 2026 lists manufacturing, semiconductor, defense and energy among the targeted sectors.

How do ARTEX agents get in through suppliers?

They map which companies trust each other, break into a weaker supplier, pipeline or software provider, and use that trust: vendor logins through B2B federation, cloud trust from a partner tenant or an old access key.

How fast is an ARTEX intrusion?

The FBI says some intrusions reached privileged access in under three hours. At Barracuda the attacker touched about 10 cloud accounts in about 44 hours.

Should we take our PLM system off the internet?

Keep PLM servers, CAD vaults and admin pages behind identity-gated or Zero Trust access, and give suppliers access only to the parts they need.

More on this story