Malicious Code Injection in certain_sole_z3n: A Threat to npm Packages
Summary
MAL-2025-93497: Malicious code in certain_sole_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 certain_sole_z3n package 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 through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the certain_sole_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a polluted npm registry and potentially expose users to further security risks. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall certain_sole_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 certain_sole_z3n package by using npm's package-lock.json file to lock down your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The certain_sole_z3n package poses a significant threat to the integrity of the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for certain_sole_z3n →
FAQ
The certain_sole_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially exposing your project to further vulnerabilities.
You should uninstall the certain_sole_z3n package immediately using 'npm uninstall certain_sole_z3n' and monitor your project for any further vulnerabilities.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
