The Update Nobody Approved

It's 7:40 on a Tuesday. Your lead developer opens her laptop to finish a change to the connector between the ERP and the scheduling screens on the floor.

Her code editor loads. In the corner, a few extensions update themselves.

She doesn't notice. Nobody would.

That laptop holds a lot:

  • A key to the historian server.
  • Cloud credentials for the integration service.
  • A token that can push code to every repository your team owns.
  • A VPN profile that reaches the plant network.

One of those updates isn't what it claims to be. Within a minute of the editor opening, it has copied every key and token on the laptop and sent them out.

She finishes the connector change, pushes her code, and heads to a production meeting.

That night, the repository token gets used. A commit lands in the integration repository under the name "build-bot." It adds a small workflow that quietly copies the secrets the build pipeline depends on: the ERP database login, the cloud deployment keys, the service account for the scheduling integration.

Nothing breaks. The line runs. The schedule posts on time.

Nine days later, someone notices a workflow run nobody remembers creating. By then, everything that laptop and that pipeline could reach has been in someone else's hands for more than a week.

Now ask a simple question. Who approved that update?

IT assumes the developers manage their own tools. The developers assume IT secures the laptops.

Both answers are reasonable. Together, they mean nobody owns it.

What Happened Back in May of '26

That chain isn't made up. In May 2026, it played out in public, at companies with far deeper security teams than most manufacturers will ever have.

On May 11, a contributor to Nx, a widely used set of developer tools, installed packages for an unrelated project. One package had been poisoned that same day. It ran during the install and took the GitHub token stored on the laptop.

The project had a setting meant to block brand-new packages. The tool version it pinned was too old to read that setting, so the safeguard was skipped without a warning.

A week later, the attacker used that token to publish a poisoned version of Nx Console, a popular extension for the VS Code editor. It went out under a trusted contributor's name and passed the marketplace's automated checks.

Editors with auto-update pulled it in without a single click. Once running, it went looking for SSH keys, cloud credentials, and tokens.

CISA later reported that this extension reached a GitHub employee's device. From there, attackers copied thousands of GitHub's own internal repositories.

What caught the poisoned release? Not a security tool. A routine "your extension was updated" email that one Nx maintainer happened to read.

The attacker never had to break GitHub's defenses. They came in through a developer's editor.

1. The Assumption: Dev Tools Are a Productivity Choice

Most IT leaders treat editors, extensions, and code packages as the developers' business.

  • Developers pick the tools that make them faster.
  • IT secures the laptop, the network, and email.
  • Nobody reviews an editor extension the way they review a firewall rule.

2. Why That Belief Made Sense

For years, it worked well enough.

  • Extensions save real hours, and good developers use a lot of them.
  • Marketplaces look curated, with verified publishers and big install counts.
  • Your developers are trusted people. They should be.

3. Why It No Longer Holds

The tool isn't the risk because it's bad. It's the risk because of where it runs.

  • An extension runs as the developer. It can reach everything she can reach.
  • It doesn't need a click. Auto-update installs it. Opening the editor runs it.
  • A trusted name is the disguise. The Nx release came from a real contributor's account.
  • Pipelines are in play too. That same week, a campaign called Megalodon pushed thousands of fake "build-bot" commits that added secret-stealing workflows to build pipelines.

4. What It Costs in a Plant

A developer at a manufacturer usually isn't building a website. She's building the glue between the business and the floor.

  • The ERP-to-MES connector that tells the line what to run.
  • The scripts that pull data off the historian and into reports.
  • Credentials for servers one hop from the controls network.

In a plant, a stolen developer key rarely looks like a security event at first. It looks like nothing at all.

The cost shows up after. A week of rotating credentials, rebuilding laptops, and reviewing every recent change to code that feeds production.

A schedule nobody fully trusts until someone proves it clean. And one hard question: which machines had it, and what could they open?

5. A Better Way: Every Update Is a Deployment

Your plant already knows how to handle this. Nobody pushes a PLC program change to a running line without knowing the version, who approved it, and how to roll it back.

The developer toolchain deserves the same discipline. Not a lockdown. Change control, sized for a small team.

Every update is a deployment. Treat it like one.

  • Know what's installed. Keep a short approved list of extensions and tools. Anything outside it starts a conversation, not a reprimand.
  • Slow down what's brand new. Turn off silent extension updates, or hold new versions for a few days. Then confirm the setting actually works.
  • Keep keys off the laptop. Use short-lived, narrowly scoped credentials, pulled in when needed instead of left in files.
  • Put a second person on releases. Require approval before anything publishes or deploys. Pin pipeline steps to exact versions.
  • Read the logs you already have. Unfamiliar workflow runs and "bot" commits are exactly the trail these attackers left.

6. How We Approach It

At InsITe, we work alongside internal dev teams, not over them. We start by mapping what a developer laptop can actually reach, across IT and the plant floor.

Then we build guardrails with the developers who will live with them, so the controls stick. The goal is one clear owner for the toolchain, not another gap between IT and everyone else.

The Landing

The May attacks didn't break through anyone's firewall. They rode in on tools that updated themselves and ran with a developer's full trust.

Your plant would never accept that on the line. There's no reason to accept it on the laptop that writes the code the line runs on.

Every update is a deployment.

Two questions to sit with:

  • If an extension updated on your lead developer's laptop this morning, would anyone know? Who approved it?
  • If that laptop's keys were stolen tonight, how long would it take your team to list everything they could open?

ABOUT INSITE BUSINESS SOLUTIONS:

Most West Michigan manufacturers know they need to connect their shop floor systems with their business systems. But figuring out how to bridge that gap is like playing vendor roulette. They often end up picking either an IT shop or an automation house, or a combination of both. 

InsITe has IT and OT engineers on staff. One call, one team, one point of accountability across the full tech stack. Before we recommend anything, we walk your shop floor and then design the solution, execute the implementation, and own the outcome through managed services, security, and ongoing support. 

If you're looking for IT or OT help from people who understand the ins and outs of manufacturing, we can help. 

Talk to an Advisor Today →

Back to Blog