Malicious Code Injection in different_tortoise_z3n Package: npm Vulnerability Overview
Summary
MAL-2025-98676: Malicious code in different_tortoise_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The different_tortoise_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's primary function is to facilitate the distribution of JavaScript code, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the different_tortoise_z3n package stems from its inclusion in a malicious campaign that generates and publishes derivative packages with altered metadata. The malicious code modifies the package.json file to remove private flags, changes version numbers, and creates random package names, which leads to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall different_tortoise_z3nIf 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 prevent the installation of the different_tortoise_z3n package by using the following command: npm uninstall different_tortoise_z3n. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to detect open-source vulnerabilities in real-time.
Conclusion
The different_tortoise_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for different_tortoise_z3n →
FAQ
The different_tortoise_z3n package is an npm package that has been associated with a malicious campaign aimed at inflating developer reputation scores through the publication of compromised packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.
If you have installed the different_tortoise_z3n package, you should immediately uninstall it and monitor your application for any unusual behavior.
You can use Vulert to monitor your application for open-source vulnerabilities by analyzing your package-lock.json file. This tool provides real-time alerts for any detected vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
