Malicious Code Injection in dependent_marten_z3n: A Threat to npm Users
Summary
MAL-2025-101350: Malicious code in dependent_marten_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 'dependent_marten_z3n' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards associated with the tea protocol, but it has been compromised to include malicious scripts that can harm users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'dependent_marten_z3n' originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the security of the affected packages but also poses a risk to developers who may unknowingly install these malicious versions, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dependent_marten_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 measure, you can avoid using the 'dependent_marten_z3n' package until a secure version is released. Additionally, consider using the following command to uninstall the package: 'npm uninstall dependent_marten_z3n'. This will help mitigate the risk while waiting for a patch.
Conclusion
The 'dependent_marten_z3n' package poses a significant threat due to its malicious code that manipulates the npm registry. Users are advised to take immediate action by updating or uninstalling the package and utilizing tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential for maintaining the security of your projects.
See every vulnerability recorded for dependent_marten_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed this package, it is recommended to uninstall it immediately and check for any updates or patches.
While specific exploits have not been detailed, the nature of the vulnerability allows for potential misuse by malicious actors to compromise systems.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
