Tampered AI Coding Add-On Reached Up to 5,000 Developers

A tampered copy of an official AI coding add-on sat in a code editor's marketplace for about 11 to 12 hours on Oct 29 and reached at most 5,000 users.
A tampered copy of an official AI coding add-on was published in a coding tool’s add-on marketplace. It stayed live for about 11 to 12 hours on Oct 29 (WIRED says about 11 hours, Ars Technica nearly 12) and reached at most 5,000 users.
According to Ars Technica (Oct 30, 2026) and WIRED (Oct 30, 2026).[1] [2]
What happened
The add-on connects a popular AI assistant to a code editor. A tampered copy of it was published in one editor’s add-on marketplace.[1] [2]
How that happened is still unclear. Ars Technica reports that the bad version was posted through the add-on’s official account in that marketplace, and that it is not yet known how the attackers got that access.[1] WIRED reports that staff at the add-on’s maker said their own systems were not compromised, and that someone used access to the marketplace to publish the tampered copy.[2]
Ars Technica notes that add-ons in that editor update automatically by default, so machines could fetch the bad version without anyone clicking anything.[1]
The marketplace operator said the malicious version affected “at most 5,000 users.”[1] [2] According to Ars Technica, it removed the version, blocked further downloads and worked to cut off the server the malware tried to reach.[1]
Timeline
According to Ars Technica, the tampered release was numbered 2.1.313 and replaced the genuine 2.1.312. Anyone who installed or updated the add-on between about 5:27 am and 4:35 pm US Eastern time on Thursday, Oct 29 should consider themselves affected.[1]
The marketplace was briefly shut down afterwards: WIRED says while its operator investigated, and Ars Technica says to change its keys and check that no other add-ons were affected.[1] [2]
What the malware tried to do
The tainted add-on was built to plant a hidden back door that would give attackers access to the machine. It was written for all the main desktop operating systems.[1] [2] Ars Technica reports that it tried to add an attacker’s login key, switch on remote login and open a tunnel back to the attackers.[1]
A flaw in the malware’s own code stopped the back door from fully setting itself up on most machines, a lucky break for many developers.[1] [2] Ars Technica says that step failed unless the editor was running with administrator rights. That is luck, not protection: a security researcher quoted by Ars still called the malware a significant threat.[1]
According to Ars Technica, before trying the back door the malware gathered basic details about the computer and its user, plus the names of the computer’s environment variables, which on developer machines often point to stored keys. It also tried to make itself start again after a restart, and kept retrying about once a minute to reach a server controlled by the attackers.[1]
How to check your machine
If you use that editor and the add-on, check which version is installed. Ars Technica identifies 2.1.313 as the bad one.[1] Remove it, or move to a newer release from the official publisher, and follow the clean-up steps the marketplace operator published.[1] [2] Then look for login keys or startup items you did not add yourself, and remove them. If in doubt, ask your security team to check the machine, and change any cloud keys, tokens and passwords that were stored on it.
Why it matters
Developers’ machines often hold cloud keys, source code and passwords. A back door there can be a stepping stone deeper into a company’s network.[1] [2]
The tampered copy appeared under the official add-on’s account.[1]
The short version
This was not a look-alike with a different name. It was a tampered copy of an official add-on that installed itself as an update. If you installed or updated that add-on in the affected window, treat the machine as exposed: follow the vendor’s clean-up steps and change keys stored on it.
One simple habit also helped here: the back door mostly failed on machines where the editor did not run with administrator rights. Day-to-day coding rarely needs those rights, so keep them switched off unless a task truly needs them.
How to stay safe
- Turn off automatic add-on updates on work machines.
- Act fast on security alerts for the tools you use.
- Keep cloud keys and passwords out of plain files on developer machines.
- Change any keys stored on a machine that ran a bad update.
- Install only add-ons you really need, and remove the rest.
Follow AI Safe Mode
Protect yourself with Privaku
- Privaku AI Shield (Mac) watches what AI agents do on your computer and flags risky actions: https://privaku.com/agent-shield/
See the post on YouTube Watch and follow AI Safe Mode on YouTube @AISafeMode and Instagram @aisafemode.
References
- Ars Technica, Oct 30, 2026. Report on the backdoored add-on. Read the report ↗
- WIRED, Oct 30, 2026. Report on the supply-chain attack. Read the report ↗
