npm

The @atedone/workspace-context npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 1 Nov 2026

@atedone/workspace-context 0.0.12 to 0.0.25 on npm change the shell setup when loaded, and 0.0.25 runs prompt text from 150.136.8.159.

GitHub and OpenSSF flag versions 0.0.12 to 0.0.25 as malware. Amazon Inspector found the code.

What happened

The npm account atedone published a package that changes the shell when a program loads it.

  • In 0.0.25, index.js calls state.initialize() on require(). No install script is needed.
  • It writes init.zsh, .zshrc, presentation.js and channel.json into ~/.config/workspace-context.
  • It starts a detached /bin/zsh -i with ZDOTDIR set to that folder.
  • The session sends the user name to 150.136.8.159 on port 8080 and saves the reply as session-profile.json.
  • It turns on setopt prompt_subst and puts the reply text into PROMPT unescaped. With that option, zsh runs any command text inside the prompt.

We read 0.0.12 and 0.0.25. Version 0.0.12 runs worker.js on load, which adds a line to .zshrc or .bashrc. It contains no network code. The advisories list 0.0.12 as malicious. The registry shows 0.0.12 on 1 November 2026 and 0.0.25 on 2 November 2026.

Affected versions

  • @atedone/workspace-context 0.0.12 to 0.0.25 (GitHub advisory)
  • OpenSSF also lists the range 0.*
  • No fixed version exists

Indicators of compromise

  • http://150.136.8.159:8080/workspace/profile
  • ~/.config/workspace-context
  • ~/.workspace-context
  • lib/state.js SHA-256 e683a53424f9f5d39de6712865b11ce7296c3fa0ffb90f8be2862b9e44fd7486

How to check

List the package in each project.

npm ls @atedone/workspace-context

Look for the shell files in your home folder.

ls -la ~/.config/workspace-context ~/.workspace-context

What to do now

  1. Remove @atedone/workspace-context from every project and lockfile.
  2. Stop any zsh or node process that uses ~/.config/workspace-context, then delete both folders.
  3. Delete the workspace-context line from ~/.zshrc or ~/.bashrc.
  4. From a clean computer, rotate every secret on the affected machine, as the GitHub advisory says.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `@atedone/workspace-context` 0.0.12. This version is too new or changed in a way Vigilance must check first.
The last safe version is 0.0.11. Install that version.

In the owner report

Bad update

@atedone/workspace-context 0.0.12

This update now downloads from the internet. The version before it did not.

  1. Ask the AI tool to swap @atedone/workspace-context to 0.0.11. That is the last safe version.

Frequently asked questions

Is @atedone/workspace-context malware?

GitHub advisory GHSA-39ch-q3p3-3j33 and OpenSSF record MAL-2026-18517 flag versions 0.0.12 to 0.0.25 as malicious code.

How many people downloaded @atedone/workspace-context?

The npm download count shows 3,578 downloads from 30 October to 1 November 2026.

Sources

  1. github.com/advisories/GHSA-39ch-q3p3-3j33
  2. osv.dev/vulnerability/MAL-2026-18517
  3. registry.npmjs.org/@atedone/workspace-context
  4. unpkg.com/@atedone/workspace-context@0.0.25/lib/state.js
  5. unpkg.com/@atedone/workspace-context@0.0.25/lib/sync.js
  6. unpkg.com/@atedone/workspace-context@0.0.12/lib/state.js

More supply chain attacks

All 145 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library