motion-forge-cssnpm
motion-forge-css is a confirmed malicious npm package (MAL-2026-11101) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in motion-forge-css (npm)
What this malware does
Package advertises itself as a small PostCSS vendor-prefix / CSS-variable-injection plugin but ships a single ~105KB obfuscator.io-packed bundle as its main entry (index.js), loaded on every require('motion-forge-css'). The bundle uses a 912-entry rotated string array, string-decoder, self-defending / anti-debug wrapper, and an inline base64 alphabet — none of which are required to add CSS vendor prefixes. The bundle also contains a plaintext Function( dynamic code-construction primitive alongside string-array entries for require, Buffer, process, constructor, and prototype, which is the standard toolkit for reconstructing Node built-ins by name and executing a decoded payload at import time. The combination of deep obfuscation, dynamic-code-execution primitives, and runtime lookup of Node internals in a package whose stated purpose is trivial text substitution is inconsistent with a legitimate CSS plugin and matches the shape of a hidden install/require-time loader.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for motion-forge-css (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging motion-forge-css across your stack and pipelines.
If you installed it — respond
Remove motion-forge-css from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If motion-forge-css was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks motion-forge-css before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks motion-forge-css-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.