Malicious Code Injection in close_puma_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-93588: Malicious code in close_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 close_puma_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. It is designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the close_puma_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The primary risk includes the pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially lead to further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall close_puma_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 the close_puma_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the installation of this malicious package until it is fully addressed.
Conclusion
The close_puma_z3n package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to remove this package from their projects and monitor for any vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for close_puma_z3n →
FAQ
The close_puma_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for fraudulent purposes.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further security risks.
If you have installed the close_puma_z3n package, you should uninstall it immediately using 'npm uninstall close_puma_z3n' and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software without requiring access to your code. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
