Malicious npm package mayx-blog — full system compromise on install
Severity: critical · Patch status: no-fix-needed · Since 2026-11-20
GitHub's malware advisory database published GHSA-gmwr-j73c-6xw3 on 2026-11-20 flagging the npm package mayx-blog version 1.0.0 as embedded malicious code (CWE-506). Per the advisory, any computer where the package is installed or running should be considered fully compromised, with full control potentially handed to an outside entity. No patched version exists; the advisory recommends removal, but notes removal cannot guarantee elimination of all malicious software left behind. The package shows 42 GitHub stars, suggesting some real-world reach. Anyone who installed mayx-blog 1.0.0 should treat all secrets and keys on affected machines as stolen and rotate them from a clean computer.
What to do
- Remove mayx-blog from all systems and rebuild affected machines from clean images
- Rotate all secrets, keys, tokens and credentials stored on or accessible from affected machines, using a different clean computer
- Audit systems for persistence mechanisms and unauthorized access following installation
- Check CI/CD and developer environments for exposure of npm tokens, SSH keys and cloud credentials
Sources
All live incidents on Threat Watch