GitHub and OpenSSF mark all versions of motionframe-plugins as malware, and npm removed them on 20 November 2026.
GitHub advisory GHSA-8j58-xfpr-cqfv marks every version of the npm package motionframe-plugins as malware. npm replaced the package with a security holding package on 20 November 2026.
What happened
GitHub published malware advisory GHSA-8j58-xfpr-cqfv on 20 November 2026. OpenSSF copied it as MAL-2026-20298.
- The advisory affects every version, with no patched version.
- The advisory gives no payload, file, domain or hash.
- The registry listed seven releases, 1.0.2 through 1.0.7, all published on 17 November 2026.
- npm published the security holding version 0.0.1-security at 12:29:11 UTC on 20 November 2026.
- The registry no longer serves versions 1.0.2 through 1.0.7.
The code was unavailable for inspection. No fetched source names the first malicious release.
Affected versions
- GitHub and OpenSSF: all versions (introduced 0, no fix).
- Registry history: 1.0.2 through 1.0.7, all published 17 November 2026, now removed.
How to check
List the installed version in each Node.js project.
npm ls motionframe-plugins
Search package-lock.json files in past builds for the package name. Those builds can show when an install pulled a removed version.
What to do now
- Run
npm uninstall motionframe-pluginsin every project. - The advisory says to treat a computer with the package installed or running as fully compromised.
- From a different computer, rotate the secrets and keys stored on it.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `motionframe-plugins` 1.0.7. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
motionframe-plugins 1.0.7
A three-day-old npm package was removed by npm after GitHub marked all its versions as malware.
No security team? See who reads the alert.
Frequently asked questions
What does the motionframe-plugins malware do?
No fetched source describes the payload. The advisory only says a computer with the package installed or running is fully compromised.
Is motionframe-plugins still on npm?
No. npm removed versions 1.0.2 through 1.0.7 and now serves a security holding version, 0.0.1-security.
Sources
Send this page to the person who looks after AI at your company.