Malicious Code Injection in noble_tortoise_z3n: A Threat to npm Users

noble_tortoise_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88862: Malicious code in noble_tortoise_z3n (npm). Affected versions are not published. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

noble_tortoise_z3n is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and flood the npm registry with unwanted packages.

Vulnerability Detail

The vulnerability in noble_tortoise_z3n stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious code can inflate developer reputation scores fraudulently, posing a risk to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall noble_tortoise_z3n

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

As a temporary workaround, you can remove the noble_tortoise_z3n package from your project by executing: npm uninstall noble_tortoise_z3n. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The noble_tortoise_z3n package has been compromised with malicious code that poses a significant risk to npm users. It is crucial to update or remove the package to protect your projects from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for noble_tortoise_z3n →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata to inflate developer reputation scores and pollute the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

You can temporarily uninstall the package to prevent any malicious code from executing until a fix is available.

The malicious code can lead to the publication of unwanted packages, potentially harming your project's reputation and security.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall noble_tortoise_z3n

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