Malicious Code Injection in normal_mule_z3n Package
Summary
MAL-2025-95662: Malicious code in normal_mule_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 normal_mule_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages often contain scripts that manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the normal_mule_z3n package originates from its association with the tea.xyz token reward campaign. The package includes malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising other packages and applications that depend on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall normal_mule_z3n
If 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, avoid using the normal_mule_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your package dependencies for any updates or vulnerabilities.
Conclusion
The normal_mule_z3n package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for normal_mule_z3n →
FAQ
The normal_mule_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and applications that rely on normal_mule_z3n or its derivatives.
If you have installed the normal_mule_z3n package, you should uninstall it immediately using the command npm uninstall normal_mule_z3n.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.