Malicious Code Injection in prepared_roundworm_z3n: A Threat to npm Packages
Summary
MAL-2025-95991: Malicious code in prepared_roundworm_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 'prepared_roundworm_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'prepared_roundworm_z3n' stems from its malicious payload that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of other packages relying on this ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prepared_roundworm_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 this malicious package by using the following command: 'npm uninstall prepared_roundworm_z3n'. Additionally, ensure to monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'prepared_roundworm_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for prepared_roundworm_z3n →
FAQ
The malicious code can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and reputation.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
If a patched version is not available, it is advisable to remove the package from your project to mitigate the risk.
This vulnerability can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially leading to dependency confusion.
Signs of compromise may include unexpected changes to your package.json file, the presence of unfamiliar package names, or unusual behavior in your application.
