# MAL-2026-11168: Malicious code in postcss-motion-utils (npm)


- **Type:** Malicious package
- **Package:** `postcss-motion-utils` (npm)
- **Published:** 28 Jul 2026
- **Also known as:** GHSA-m763-9wch-p9gg

## What is MAL-2026-11168?

MAL-2026-11168 is a malicious package in postcss-motion-utils, published on 28 Jul 2026. 

### Official description

Package is advertised as a small PostCSS plugin that injects CSS variables and adds -webkit- prefixes, but its `main` (index.js) is a 164 KB single-file Bun-bundled artifact wrapped in a bytecode-VM obfuscator: a rotated string array (`vmZ`) with a shift-based decoder, a VM interpreter (`vmT_21dbca`), and a payload table of ~20 large base64 blobs, several of which decode to opaque binary-shaped bytes. The file begins with the `// @bun` header and a `while(!![])` string-array rotation loop. Because this file is the module main, the VM and its embedded payloads execute on `require('postcss-motion-utils')`. The declared PostCSS functionality does not require bytecode-VM obfuscation or embedded binary blobs; the shape (opaque decoder + rotated string array + base64-encoded inner payloads executed at import) matches the structure of hidden supply-chain payloads rather than a CSS utility library.

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-11168?

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-11168 is a malicious package: postcss-motion-utils (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-11168/ (Markdown: https://insights.sbomify.com/MAL-2026-11168/index.md)
```

## Sources

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

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