Malicious Code Injection in substantial_sole_z3n: A Threat to npm Packages
Summary
MAL-2025-90785: Malicious code in substantial_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 package substantial_sole_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to automatically generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in substantial_sole_z3n originates from its association with a malicious campaign that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall substantial_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 measure, you can avoid using the substantial_sole_z3n package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.
Conclusion
The substantial_sole_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for substantial_sole_z3n →
FAQ
substantial_sole_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
If you have installed substantial_sole_z3n, you should uninstall it immediately using the command 'npm uninstall substantial_sole_z3n'.
Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and only install packages from trusted sources.
Yes, you can use the Vulert playground at Vulert Scanner to check your package-lock.json for vulnerabilities without any installation or signup.
