Critical Malicious Code Vulnerability in @ntnx/t Package

@ntnx/t Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191036: Malicious code in @ntnx/t (npm). Affects @ntnx/t versions 0.0.101. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @ntnx/t package is a Node.js library available through npm, designed for specific functionalities within the Nutanix ecosystem. It is used for various tasks related to cloud infrastructure management. However, this package has been identified to contain malicious code, posing a significant risk to systems that utilize it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @ntnx/t package, specifically version 0.0.101. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full system compromise, making it imperative for users to take immediate action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @ntnx/t

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no workarounds that can mitigate the risks associated with this vulnerability. The best course of action is to uninstall the package entirely.

Conclusion

The @ntnx/t package has been identified as containing malicious code, leading to severe security risks for any system utilizing it. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for @ntnx/t →

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall @ntnx/t' and rotate any sensitive information stored on the affected machine.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, there is currently no patched version available for the @ntnx/t package. The only solution is to uninstall it.

Failing to address this vulnerability can lead to full system compromise, unauthorized access to sensitive data, and potential exploitation by malicious actors.

While not all packages in the ecosystem are compromised, it is crucial to review and monitor all dependencies for vulnerabilities regularly.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @ntnx/t

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback