Cloudanix Joins AWS ISV Accelerate Program

Cloudanix – Your Partner in Cloud Security Excellence

Extension Confusion: The IDE Supply Chain Risk Hiding in Your AI Editor

  • Purusottam Mupunu Purusottam Mupunu
  • Thursday, Nov 19, 2026

You install a new AI code editor. It offers to import your extensions and settings from VS Code. You click yes. Everything looks exactly like yesterday.

That click is where a supply chain risk called extension confusion begins. On a recent episode of Scale To Zero, I talked with Raj Handa, Senior Cybersecurity Engineer in offensive security at Workday, where he leads the pentest program and runs bug bounty. Raj introduced extension confusion at the Bay Area OWASP August meetup.

Here are the practical parts of that conversation, for anyone who owns developer tooling, endpoint security, or AppSec.

What Is Extension Confusion?

Modern developer tooling is split across two extension ecosystems.

VS Code pulls extensions from Microsoft’s Visual Studio Marketplace, whose terms, as Raj explained, restrict it to official Microsoft products. So AI-first editors such as Cursor and Windsurf typically turn to Open VSX, an open source registry run by the Eclipse Foundation.

Both registries use the same naming scheme: publisher.extension. But they do not share accounts, namespaces, or ownership.

“A name on one registry has zero legal or, I would say, cryptographic link to the same name on the other.” (Raj Handa)

Here is how the attack plays out, as Raj described it:

  1. A developer installs a new AI editor and imports their extensions from VS Code.

  2. The editor copies the local extensions but points future updates at Open VSX.

  3. If one of those extensions was never registered on Open VSX, its namespace there is orphaned. An attacker claims the name and publishes a higher version.

  4. Auto-updates are on by default, so the editor quietly downloads the attacker’s version in the background.

“Zero clicks, no prompt, and no warning.”

Extensions are not sandboxed. They run in your developer context and inherit your shell, SSH keys, secrets, and cloud tokens. Raj said a benign test he ran against unclaimed namespaces kept getting callbacks from managed corporate laptops for over 60 days.

Open VSX’s namespace documentation notes that extensions in namespaces without an owner are shown as unverified with a warning icon. That helps a human who looks. Fewer and fewer installs involve a human looking.

How Is It Different From Dependency Confusion?

Dependency confusion tricks the build: a package manager looking for an internal library queries PyPI or npm by mistake and pulls a higher public version.

“Extension confusion moves that trick up to the editor level.”

Dependency confusion is an internal versus public problem. Extension confusion, as Raj put it, is an ecosystem fracture between two parallel public registries: the attacker takes a trusted public tool from one store and exploits the fact that another public store lets anyone claim that identity.

Doesn’t Registry Scanning Solve This?

Raj’s answer was “yes and no.” Scanning is a good first step, but he noted that attackers have already slipped credential-stealing payloads hidden with invisible Unicode past Open VSX scanning. You still need complementary controls.

Why the Editor Is a Security Blind Spot

We scan libraries, sign commits, and harden CI/CD. Raj’s view is that the problem is where we drew the trust boundary.

“We spent decades hardening the factory, but we left the workbench wide open.”

The editor sits upstream of every pipeline control, on a laptop that holds keys to production. Raj gave three reasons this is so dangerous:

  • Zero sandboxing. An extension runs with the developer’s full permissions: environment files, tokens, uncommitted code, cloud credentials, SSH keys.

  • Detection asymmetry. Developer laptops are noisy, so odd outbound traffic gets written off as normal activity.

  • Workstations treated as scratch pads. We assume risk starts at merge. With AI-assisted IDEs, Raj argued, the workstation is effectively production-like.

AI Agents and Devcontainers Remove the Human

Raj thinks this is getting worse. Traditionally an attacker still needed a human to ignore an unverified publisher and click install.

Now you clone a repo, click “trust folder,” and the editor installs whatever devcontainer.json or extensions.json lists, resolved strictly by name. Nobody checks the publisher badge. Coding agents go further, deciding they need a linter or formatter and installing it by name on the fly.

“When you bring autonomous coding agents into your environment, you do not really apply any human skepticism.”

Real-World Signal: 77 Evil Twins on Open VSX

In August 2026, Manifold Security reported 77 counterfeit “evil twin” extensions on Open VSX, each copying the name, namespace, and description of a real VS Code Marketplace extension and beaconing to the same new domain.

Nineteen sent details like the git remote, commit email domain, workspace path, branch, and CI project identifiers, described in the listings under “Telemetry.” Manifold says the packages were removed from Open VSX as of August 3, 2026. Raj’s read:

“An extension beaconing out with internal Git metadata doesn’t really look like an intrusion. It just looks like developer noise.”

What Security Teams Should Lock Down

Raj gave three core controls. The last two items follow from the rest of our conversation.

Extension Security Checklist

  • Allowlist by verified publisher ID, not by name. “If your policy is only checking the name string, you have secured nothing,” Raj said. Install only when both the approved extension ID and the verified publisher match.

  • Resolve from an internal mirror. Treat extensions like enterprise Python or npm packages: mirror internally, curate what enters, and point editors only at that source.

  • Turn off silent auto-updates and pin versions. Counterintuitive, but the risk is an extension that is benign on Monday and updates itself into a malicious payload on Tuesday morning. Pinning buys time to detect it.

  • Audit repo-driven installs. Review what devcontainer.json and extensions.json ask editors and agents to install.

  • Keep secrets off the workstation. Fewer long-lived credentials on laptops means a smaller blast radius.

For VS Code, Microsoft documents an extensions.allowed setting and AllowedExtensions policy that allow or block by publisher, extension ID, and version. Check what your AI editor offers before rollout.

Who Owns This?

Extension confusion slips through partly because nobody clearly owns the editor. AppSec owns the pipeline, endpoint teams own the laptop, and developers own their setup.

Raj’s framing points to an answer: platform teams should own extensions the way they own package registries. One practical split: platform or developer-experience teams run the mirror and editor configuration, security sets the allowlist criteria and detections, and a new AI editor gets reviewed like any third-party tool before rollout.

One Bad Habit to Break

Asked by a listener for the one habit he would stop every developer from doing, Raj said: stop hard-coding an API key to test locally and promising to clean it up before you push. Extensions inherit everything on that machine.

“In software, nothing is more permanent than a temporary workaround.”

For an offensive team, those forgotten shortcuts often mean there is no need to burn a zero-day at all.

Listen to the Full Episode

The full episode also covers running a bug bounty when much of the inbox is AI-generated noise, and pentesting the third-party supply chain. On that last topic, see Raj’s Workday engineering post, Beyond the Vendor Perimeter: Strategic Pentest for Third-Party Supply Chain Attacks.

Scale To Zero is the security podcast we run at Cloudanix. If this was useful, subscribe and share it with whoever owns your developer tooling. And if your team has already locked down editor extensions, I would love to hear how.

People Also Read

What Our Users Are Saying

Customer Reviews

Cloudanix is trusted by security leaders worldwide to deliver proactive, reliable, and cutting-edge cloud security.

One day, I changed the password of a root account, and my CTO called me within less than a minute to confirm if I did so. I was not expecting a reaction this quick. He told me Cloudanix alerted him of this password change and that he wanted to confirm as it was a critical security notification. I couldn't believe it!

Ritesh Agarwal
Ritesh Agarwal
CEO, Airgap Networks

Compliance is one way of staying secure, but what I want is the ability to go deeper and attain 'true security.' Cloudanix provides us the capability to do so.

Vishal Madan
Vishal Madan
Head of Engineering, iMocha

Cloudanix is building for the future of the cloud, which makes the product all the more desirable.

Ritesh Agarwal
Ritesh Agarwal
CEO, Airgap Networks

Cloudanix gave us the visibility we were missing. Being able to move from permanent access to a robust Just-In-Time (JIT) workflow has fundamentally changed our security posture without slowing down our engineering velocity.

Pavan Kumar Lekkala
Pavan Kumar Lekkala
SRE Lead, HugoHub

We are excited to leverage Cloudanix's comprehensive multi-cloud DevSecOps solution to secure our production workloads on AWS. Cloudanix has demonstrated that it can solve many challenges that DevSecOps teams face while continually adding new features such as SOC2 compliance and drift detection.

Satish Mohan
Satish Mohan
Co-founder & CTO, Airgap Networks

Managing third-party partner access was once a major concern for our security posture. With Cloudanix JIT Cloud, we've effectively achieved zero third-party risk. We can now grant access confidently, knowing that it is temporary, audited, and automatically revoked, resulting in a 100% reduction in our privileged access exposure.

Okesh Badhiye
Okesh Badhiye
Head of Technical Engineering, Finfinity

The snooze feature and responsible alerts have helped us save time and prioritize what to tackle first.

Satish Mohan
Satish Mohan
Co-founder & CTO, Airgap Networks

Implementing Cloudanix JIT internally allowed us to practice what we preach. By eliminating permanent access to our own clouds and databases, we've neutralized the risk of standing privileges, ensuring our own 'keys to the kingdom' are never left exposed.

Girish Manghnani
Girish Manghnani
Managing Partner, Tech Inspira

The problem with permissions is a lot of times, the gaps are left open due to oversights from inside the organization itself. With Cloudanix's CIEM, we get a complete view of user permissions and access. This enables us to update the permissions, reducing the attack surface.

Nilesh Pethani
Nilesh Pethani
Application Architect, iMocha

In the world of Fintech, trust is our currency. Cloudanix provided the frictionless visibility we needed to secure our EKS workloads across AWS, ensuring we stay audit-ready for SOC2 and GDPR without slowing down our engineering velocity.

Amol Naik
Amol Naik
Head of Security & Infrastructure, HugoHub

Cloudanix delivered value within 5 minutes of onboarding. Continuous monitoring, timely detection, and excellent documentation helped us attain a great cloud security posture.

Divyanshu Shukla
Senior DevSecOps, Meesho

Technology strategies and business strategies are in a state of constant change which includes centralization and decentralization of responsibilities. Regardless of strategic shift, we still have intellectual property to protect. Cloudanix are critical partners for us in our public cloud security posture across our three cloud providers.

Jerry Locke
Jerry Locke
Senior Director Global Solutions Engineering, Eversana

Cloudanix has been amazing. They opened up a common Slack channel with us — and it feels like we are talking to our own team and getting things done with Cloud security. The support team is always available, friendly, helpful, and ready to go out of their way.

Satish Mohan
Satish Mohan
CTO, Airgap Networks

Beyond just access management, Cloudanix CSPM has given us a unified view of our AWS environment. The real-time alerting and anomaly detection allow us to prevent any untoward activity before it happens, which is critical for a marketplace connecting 50+ financial institutions.

Okesh Badhiye
Okesh Badhiye
Head of Technical Engineering, Finfinity

For a Fintech company, data is our most valuable — and most sensitive — asset. Cloudanix DAM hasn't just improved our visibility; it has given us control. The ability to mask data and prevent unauthorized queries in real-time is a game-changer for our compliance and customer trust.

Jiten Gala
Jiten Gala
President Engineering and Product, Kapittx

Our clients, especially in the Middle East financial sector, demand absolute accountability. Cloudanix JIT Cloud has been a competitive differentiator for us, allowing us to provide secure, governed access to customer accounts that meet their strictest audit and compliance requirements.

Girish Manghnani
Girish Manghnani
Managing Partner, Tech Inspira

Cloudanix is always on my team's lips because of its exceptional support. Be it a small or big query, Cloudanix has gone above and beyond to resolve them. This one's a keeper for us.

Sujit Karpe
Sujit Karpe
CTO, iMocha

For a long-lasting partnership, great support goes a long way. Cloudanix has delivered exceptional support whenever required. Their edge is their team is always ready to go beyond to solve any issues that we have. This speaks volumes about the culture at Cloudanix.

Akash Maheshwari
Akash Maheshwari
Co-founder, MoveInSync

Beyond the technology, Cloudanix feels like an extension of our own team. Their willingness to stand up a dedicated Middle East tenant for us and provide exceptional support at a sensible price makes them a long-term partner for Hugosave.

Surya Tamada
Surya Tamada
CTO, HugoHub

The real-time notifications that Cloudanix provides are a real lifesaver. Their adaptive notifications ensure that my team stays productive and doesn't get interrupted all the time.

Digvijay Singh
Staff Security Engineer, Meesho

The whole point in technological evolution is to help improve the world we live in. We must protect that and to do so requires an effective and efficient security strategy. The Cloudanix team helped make our public cloud security posture management strategy a reality. The symbiotic relationship we have allows for a continuous feedback loop which is how business should operate.

Larry Wheat
Larry Wheat
Staff Solutions Engineer, Eversana

Ready to see your graph?

Connect a cloud account in under 30 minutes. See every finding rooted in identity, asset, and blast radius — with a fix path attached.

Book a Demo