Which versions of postcss-animatecss are malicious?

The following npm versions of postcss-animatecss are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate postcss-animatecss if I installed it?

postcss-animatecss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed postcss-animatecss — how do I know if it already compromised me?

If postcss-animatecss 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.

Is postcss-animatecss part of a known attack campaign?

Yes — postcss-animatecss is associated with the IN-MAL-2026-010374, IN-MAL-2026-010373 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find postcss-animatecss across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postcss-animatecss (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postcss-animatecss across your stack and pipelines.

Malicious package

postcss-animatecssnpm

Malicious code in postcss-animatecss (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10539

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall postcss-animatecss

What this malware does

The exported PostCSS plugin factory in [email protected] contains an obfuscator.io-obfuscated payload that executes on every consumer build. When the plugin runs, it fetches a remote endpoint (URL built from an RC4/base64 string array hidden inside the module), reads a message field from the JSON response, base64-decodes it, and executes the result via new Function('require', m)(require) — giving the remote operator arbitrary Node.js code execution with full require access on the developer or CI host. A setInterval(fn, 4000) installed via a new Function('return this')() global reference re-invokes the fetch-and-eval loop every 4 seconds for the lifetime of the process, providing persistent adaptable C2. The outbound request also appends Object.keys(options.features?...) to the query string, leaking consumer plugin configuration to the endpoint. The package's declared purpose (adding -webkit- animate.css prefixes) requires no network I/O whatsoever; the fetch/eval/interval layer plus obfuscator.io string-array concealment is the classic supply-chain backdoor signature.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

738c22eca129a28069de2e6a01f1897db0f7db302e5e3bd809e3bca62ee76abd

adfcae16a606f0b7eccb6cd94c1d1d0b583b19021bb15d04161f3ca8855aba61

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postcss-animatecss (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postcss-animatecss across your stack and pipelines.
If you installed it — respond
postcss-animatecss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If postcss-animatecss 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 postcss-animatecss 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

No. postcss-animatecss on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010374IN-MAL-2026-010373

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks postcss-animatecss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring