Which versions of process-tailwind are malicious?

The following npm versions of process-tailwind are flagged malicious: 1.1.99. Treat any of these as compromised.

How do I remediate process-tailwind if I installed it?

process-tailwind 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 process-tailwind — how do I know if it already compromised me?

If process-tailwind 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 process-tailwind part of a known attack campaign?

Yes — process-tailwind is associated with the IN-MAL-2026-020063 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 process-tailwind 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 process-tailwind (version 1.1.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging process-tailwind across your stack and pipelines.

Malicious package

process-tailwindnpm

process-tailwind is a confirmed malicious npm package (MAL-2026-16179) that opens a backdoor for remote access (malicious version 1.1.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in process-tailwind (npm)

MAL-2026-16179

Immediate action

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

npm uninstall process-tailwind

What this malware does

On require/import, index.js unconditionally calls initialize(), which spawns a detached, unref'd node loader.js child with stdio ignored and writes a PID file. loader.js fetches JSON from https://api.npoint.io/24c25d5f5fcbb0992a4f (a mutable third-party paste endpoint), base64-decodes the code field, and executes it via new Function('require','__dirname','__filename','module','exports', decodedCode)(...), granting the remote endpoint operator arbitrary code execution on the installer's host. The remote URL is stored in a constant misleadingly named API_KEY and surrounded by comments describing the loader as a sandboxed educational component, contradicting the actual fetch-decode-eval behavior.

Malicious versions

1 flagged

1.1.99

Indicators of compromise (SHA-256)

d22d8ef47e17a005ea3305f7d97a3cb4de14f0a3a07e8a1e461e13d25e5e7432

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 process-tailwind (version 1.1.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging process-tailwind across your stack and pipelines.
If you installed it — respond
process-tailwind 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 process-tailwind 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 process-tailwind 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. process-tailwind on npm has been identified as a malicious package (version 1.1.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020063

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks process-tailwind-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