# MAL-2026-11101: Malicious code in motion-forge-css (npm)


- **Type:** Malicious package
- **Package:** `motion-forge-css` (npm)
- **Published:** 27 Jul 2026
- **Also known as:** GHSA-3v24-55c2-cpp9

## What is MAL-2026-11101?

MAL-2026-11101 is a malicious package in motion-forge-css, published on 27 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11101?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11101 is a malicious package: motion-forge-css (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11101/ (Markdown: https://insights.sbomify.com/MAL-2026-11101/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11101

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11101/
Summaries are generated and may contain mistakes; the official description above is the record.