Malicious Code Injection in serious_mole_z3n: A Threat to npm Packages
Summary
MAL-2025-108562: Malicious code in serious_mole_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 'serious_mole_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'serious_mole_z3n' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall serious_mole_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 prevent the installation of this package by using the following command to uninstall it: npm uninstall serious_mole_z3n. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.
Conclusion
The 'serious_mole_z3n' package poses significant risks due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for serious_mole_z3n →
FAQ
The impact includes potential security breaches, pollution of the npm registry, and loss of developer reputation due to the use of compromised packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed serious_mole_z3n, you should uninstall it immediately and monitor your package-lock.json for any unauthorized changes.
Yes, consider using reputable packages that serve similar functionalities without the associated risks of malicious code.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json, ensuring your application remains secure.
