Highnpm2 affected versions

octopus-action

octopus-action has 2 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls octopus-action.

  • octopus-action@1.0.1
  • octopus-action@1.0.0

The incident that flagged it

High

GitHub Advisory malware sweep - 2026-08-27 batch (npm `hydration-vli-ui` ELF-in-JS Linux RAT + npm `commonjs-code-token` remote-eval C2 + npm `spotify-url-resolvers` Telegram-C2 project-dir exfil + npm `octopus-action` Burp Collaborator preinstall exfil + npm `chai-plus` `taskforge-9xv` second-stage installer + PyPI `pybitjs` Lazarus/PolinRider PTH-injection + PyPI `trongridet` TRX private-key exfil + PyPI PROBABLY_PENTEST cluster (4) + npm CWE-506 boilerplate (14))

24 new GHSA malware advisories in the 24h window ending 2026-08-27. Highlights: npm hydration-vli-ui@1.0.0 ships a Linux x86_64 ELF disguised as JavaScript, on import establishes a full-featured RAT with SSH-key theft and systemd persistence; npm commonjs-code-token postinstall pulls a token from access-token-delta.vercel.app and eval()s it; npm spotify-url-resolvers archives the project directory (including .env) hourly to a Telegram bot; PyPI pybitjs is attributed to Lazarus/PolinRider with blockchain-based C2 delivery.

Versions named here: 1.0.0, 1.0.1

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

octopus-action is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Other packages in the same incident

If octopus-action is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.