Which versions of tailwindcss-motion-advanced are malicious?

The following npm versions of tailwindcss-motion-advanced are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate tailwindcss-motion-advanced if I installed it?

tailwindcss-motion-advanced 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 tailwindcss-motion-advanced — how do I know if it already compromised me?

If tailwindcss-motion-advanced 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 tailwindcss-motion-advanced part of a known attack campaign?

Yes — tailwindcss-motion-advanced is associated with the IN-MAL-2026-017004 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 tailwindcss-motion-advanced 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 tailwindcss-motion-advanced (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 tailwindcss-motion-advanced across your stack and pipelines.

Malicious package

tailwindcss-motion-advancednpm

tailwindcss-motion-advanced is a confirmed malicious npm package (MAL-2026-13604) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-motion-advanced (npm)

MAL-2026-13604

Immediate action

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

npm uninstall tailwindcss-motion-advanced

What this malware does

On require of the package's main entry, lib/utils.min.js queries Ethereum RPC endpoints (eth.blockscout.com/api, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for the latest outbound transaction from the hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, parses two IPv4 C2 hosts from the transaction's to field, fetches an XOR-encoded JavaScript payload over plain HTTP at http://<ip>:443/0x/cls, decodes it, and executes it via both eval and a detached spawn('node', ['-e', payload]). Sensitive identifiers (http, https, child_process, zlib, url, URLs, HTTP methods, header names, the attacker address) are hidden behind \uXXXX unicode escapes, and the response body and x-payload-b64 header are XOR-decoded with a per-URL key before execution. The package is presented as a Tailwind CSS plugin and has no legitimate need for Ethereum RPC access, IP derivation from on-chain data, or execution of remotely fetched code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6b8426c39ffcba11d95e8ede8085ce260dbcf8527544ce9ca3a1d7a59618f0eb

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 tailwindcss-motion-advanced (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 tailwindcss-motion-advanced across your stack and pipelines.
If you installed it — respond
tailwindcss-motion-advanced 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 tailwindcss-motion-advanced 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 tailwindcss-motion-advanced 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. tailwindcss-motion-advanced 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-017004

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-motion-advanced-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

Explore

All malware advisories How O3 detects malware Vulnerability database