Which versions of @ntnx/t are malicious?

The following npm versions of @ntnx/t are flagged malicious: 0.0.101. Treat any of these as compromised.

How do I remediate @ntnx/t if I installed it?

@ntnx/t 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 @ntnx/t — how do I know if it already compromised me?

If @ntnx/t 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 @ntnx/t part of a known attack campaign?

Yes — @ntnx/t is associated with the GHSA-96fq-r78c-hx8x, RLMA-2025-06030 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 @ntnx/t across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ntnx/t (version 0.0.101).

Malicious package

@ntnx/tnpm

Advisory published Nov 24, 2025Updated Dec 23, 2025

@ntnx/t is a confirmed malicious npm package (MAL-2025-191036) that steals credentials and exfiltrates sensitive data (malicious version 0.0.101). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ntnx/t (npm)

MAL-2025-191036

Immediate action

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

npm uninstall @ntnx/t

What this malware does

The package @ntnx/t 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

0.0.101

Indicators of compromise (SHA-256)

a56d53a5cf562204b62c1283f7cc997da367c0eb1cd09c913dcedbe5469bff6e

d6c865e873520d94446f7b67f414619c4cc93ea5be524b6c1b05ce9fc13e18cb

2865f9cc29095e84318d97631a2242512c5361ad8d820cd6212a8cb06417c92a

dd9742b34d565fe5801c75c8d86f4dbd454a577258364afafcdeac08ef1ae60d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @ntnx/t (version 0.0.101).
If you installed it — respond
@ntnx/t 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 @ntnx/t 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. @ntnx/t on npm has been identified as a malicious package (version 0.0.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-96fq-r78c-hx8xRLMA-2025-06030

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @ntnx/t-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