@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.jscallsstate.initialize()onrequire(). No install script is needed. - It writes
init.zsh,.zshrc,presentation.jsandchannel.jsoninto~/.config/workspace-context. - It starts a detached
/bin/zsh -iwithZDOTDIRset to that folder. - The session sends the user name to
150.136.8.159on port 8080 and saves the reply assession-profile.json. - It turns on
setopt prompt_substand puts the reply text intoPROMPTunescaped. 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-context0.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-contextlib/state.jsSHA-256e683a53424f9f5d39de6712865b11ce7296c3fa0ffb90f8be2862b9e44fd7486
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
- Remove
@atedone/workspace-contextfrom every project and lockfile. - Stop any
zshornodeprocess that uses~/.config/workspace-context, then delete both folders. - Delete the
workspace-contextline from~/.zshrcor~/.bashrc. - 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.
- 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.