Malicious Code Injection in different_puma_z3n: A Threat to npm Packages
Summary
MAL-2025-101562: Malicious code in different_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 'different_puma_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of such packages is to automatically generate and publish derivative versions with altered names and metadata, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'different_puma_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of harmful packages in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may contain malicious code or lead to reputation damage for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall different_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 workaround, you can avoid using the 'different_puma_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'different_puma_z3n' package poses a significant risk due to its malicious code that alters package metadata and proliferates harmful derivatives. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages from their projects.
See every vulnerability recorded for different_puma_z3n →
FAQ
The 'different_puma_z3n' package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the installation of malicious code in your project, potentially compromising security and leading to reputation damage.
You should uninstall the package immediately using 'npm uninstall different_puma_z3n' and review your project's dependencies for any other potentially malicious packages.
Regularly audit your project's dependencies, use trusted packages, and consider employing tools like Vulert to monitor for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
