Malicious Code Injection in pure_turtle_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96121: Malicious code in pure_turtle_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 package 'pure_turtle_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages. Its primary function is to facilitate the distribution of JavaScript code, but it has been compromised to include harmful scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in 'pure_turtle_z3n' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, affecting developers' ability to trust and use legitimate packages. The potential ramifications include unauthorized access to sensitive data and the compromise of software integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pure_turtle_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 remove the 'pure_turtle_z3n' package from your project by executing the following command: 'npm uninstall pure_turtle_z3n'. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The 'pure_turtle_z3n' package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard applications from potential threats.
See every vulnerability recorded for pure_turtle_z3n →
FAQ
The malicious code modifies package metadata and generates random package names to inflate developer reputation scores.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Using compromised packages can lead to unauthorized access to sensitive data, software integrity issues, and potential exploitation of your application.
Regularly updating packages, using tools like Vulert for monitoring, and auditing your dependencies can help prevent vulnerabilities.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a safe version is available.
