Malicious Code Injection in empty_puma_z3n: A Threat to npm Packages
Summary
MAL-2025-94242: Malicious code in empty_puma_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 'empty_puma_z3n' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain harmful scripts. The primary function of these packages is to manipulate the npm registry by generating and publishing derivative packages with randomized names, ultimately aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'empty_puma_z3n' stems from its malicious code, 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 can lead to significant security risks, including the potential for unauthorized access to sensitive data and the degradation of the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall empty_puma_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, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that 'empty_puma_z3n' is not included in your project dependencies. Additionally, you can use the following command to uninstall it if it is already installed: 'npm uninstall empty_puma_z3n'.
Conclusion
The 'empty_puma_z3n' package poses a significant security risk due to its malicious code that manipulates the npm registry. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your dependencies.
See every vulnerability recorded for empty_puma_z3n →
FAQ
The main threat is the malicious code that modifies package.json files and floods the npm registry with harmful packages, which can compromise the integrity of your project.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall empty_puma_z3n' and check for any other affected packages.
Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
If no patched version is available, it is advisable to remove the package from your project and look for alternative packages that provide similar functionality without the associated risks.