Which versions of tailwin are malicious?

The following npm versions of tailwin are flagged malicious: 1.0.0, 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate tailwin if I installed it?

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

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

Yes — tailwin is associated with the GHSA-vfm7-jg7w-6mwv, RLMA-2026-01604 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 tailwin 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 tailwin (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwin across your stack and pipelines.

Malicious package

tailwinnpm

Malicious code in tailwin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-332

Immediate action

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

npm uninstall tailwin

What this malware does

The package tailwin was found to contain malicious code.

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.

Malicious versions

3 flagged

1.0.01.0.21.0.4

Indicators of compromise (SHA-256)

25f1e8ebfcada6d9b8288179365d666ecc4679a549f815f6715e35fc614e03e2

1c6f42d8ac771f7de2a89b36d91afb6db0c0445c7c3b9c4c094cf74b1448343d

5fde2a118b73c5a774e3c3ba3546250335bb95c429db8291071ac54d35f55423

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

Campaign

GHSA-vfm7-jg7w-6mwvRLMA-2026-01604

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tailwin-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