Which versions of tiaan are malicious?

The following npm versions of tiaan are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate tiaan if I installed it?

tiaan is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tiaan — how do I know if it already compromised me?

If tiaan was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tiaan part of a known attack campaign?

Yes — tiaan is associated with the GHSA-wcmm-4xc5-9c5f 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 tiaan across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tiaan (version 1.0.2).

Malicious package

tiaannpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

tiaan is a confirmed malicious npm package (MAL-2025-191024) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tiaan (npm)

MAL-2025-191024

Immediate action

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

npm uninstall tiaan

What this malware does

The package tiaan 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

0135c9cc2fe2d3112342fbb4e91dee9f30647a8d8bc93c0453991d8c51f4710e

7eec9aed3f08840a4f5787d8e5edb18c097459657ba29ca488daae2047709701

6a40e19f0d67d85a82c4814f43af64ea551810d5f6b77523e23796754ab6d69a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tiaan (version 1.0.2).
If you installed it — respond
tiaan is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tiaan was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tiaan on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wcmm-4xc5-9c5f

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tiaan-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database