Which versions of animatecss-postcss-plugin are malicious?

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

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

Remove animatecss-postcss-plugin 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.

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

If animatecss-postcss-plugin 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 animatecss-postcss-plugin part of a known attack campaign?

Yes — animatecss-postcss-plugin is associated with the IN-MAL-2026-007577 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 animatecss-postcss-plugin 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 animatecss-postcss-plugin (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 animatecss-postcss-plugin across your stack and pipelines.

Malicious package

animatecss-postcss-pluginnpm

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

MAL-2026-6495

Immediate action

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

npm uninstall animatecss-postcss-plugin

What this malware does

[email protected] ships a tiny PostCSS plugin factory whose body contains an obfuscator.io-style string-array + RC4 decoder (functions _0xa311, _0x4399, _0x12b0 with a ~120-entry encoded string table). When the exported plugin factory is invoked during a CSS build, it constructs a URL from the decoded string array, performs an HTTP fetch with a 60s AbortController and a retry loop (attempts 1..10), base64-decodes the response body's message field via Buffer.from(k, 'base64').toString('utf-8'), and executes the resulting JavaScript via new Function('require', _)(require) — giving the remote payload full Node require access inside the developer's build process. There is no legitimate reason for a PostCSS prefix-injection plugin to fetch and eval remote code, and the heavy obfuscation around the fetch destination and payload-handling logic confirms intent to hide the behavior from casual review. Any project that installs this plugin and runs its CSS build will execute attacker-controlled JavaScript with the privileges of the build process.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6be12cec08d0999c157774b746c3e431825ae61635bb8ddddf36061d4602cec7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for animatecss-postcss-plugin (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 animatecss-postcss-plugin across your stack and pipelines.
If you installed it — respond
Remove animatecss-postcss-plugin 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 animatecss-postcss-plugin 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 animatecss-postcss-plugin 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. animatecss-postcss-plugin on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007577

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks animatecss-postcss-plugin-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.

Malware detection Runtime egress monitoring