Malicious Code Injection in sole_marten_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96665: Malicious code in sole_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 'sole_marten_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious behavior includes modifying package metadata and continuously republishing variants to pollute the registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'sole_marten_z3n' package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages. Furthermore, it poses a risk of unintentional dependency on compromised packages, which can lead to security breaches in applications relying on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sole_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 'sole_marten_z3n' package and any packages that depend on it. Regularly audit your package-lock.json file to identify any potentially malicious dependencies.
Conclusion
The 'sole_marten_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and pollute the registry. It is essential for developers to remove this package and remain vigilant about their dependencies to maintain the security of their applications.
See every vulnerability recorded for sole_marten_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, making it harder for developers to find legitimate packages and potentially introducing security vulnerabilities into applications.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall sole_marten_z3n' and review your project's dependencies for any other malicious packages.
Currently, there are no patches available for the 'sole_marten_z3n' package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor for open-source vulnerabilities in real-time.
