Malicious Code Injection in pretty_moth_z3n: A Threat to npm Packages
Summary
MAL-2025-89507: Malicious code in pretty_moth_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
pretty_moth_z3n is an npm package that has been identified as part of a broader malicious campaign targeting the npm ecosystem. This package, like others in the campaign, is designed to manipulate the npm registry by creating derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. However, this functionality comes at the cost of security and integrity within the npm registry.
Vulnerability Detail
The vulnerability in pretty_moth_z3n stems from its malicious payload, which 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 compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pretty_moth_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, avoid using the pretty_moth_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to identify and remove any potentially harmful packages.
Conclusion
The pretty_moth_z3n package poses significant risks due to its malicious behavior, which compromises the integrity of the npm ecosystem. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for pretty_moth_z3n →
FAQ
Using pretty_moth_z3n can lead to security vulnerabilities in your application, as it modifies package configurations and can introduce malicious code.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Immediately uninstall the package using npm uninstall pretty_moth_z3n and audit your dependencies for any other malicious packages.
Yes, consider using reputable packages that provide similar functionality. Always check the package's reputation and reviews before installation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
