Malicious Code Injection in immense_puffin_z3n: A Threat to npm Users
Summary
MAL-2025-94935: Malicious code in immense_puffin_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 immense_puffin_z3n is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to manipulate npm's publishing system, generating numerous derivative packages with the intent to inflate developer reputation scores. Its functionality is compromised by the presence of malicious scripts that can alter package metadata and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in immense_puffin_z3n originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to a significant increase in the number of malicious packages in the npm registry, potentially affecting users who unknowingly install these compromised packages. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and the risk of executing malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall immense_puffin_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, users can avoid using the immense_puffin_z3n package until a fixed version is released. Additionally, consider using a tool like Vulert to monitor your package-lock.json file 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 immense_puffin_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. Users are advised to update or remove the package and utilize monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for immense_puffin_z3n →
FAQ
immense_puffin_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your application's integrity, potentially leading to data breaches or execution of harmful code.
If you have installed immense_puffin_z3n, it is recommended to update the package to a patched version or remove it entirely until a fix is available.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
To prevent future vulnerabilities, regularly audit your dependencies, keep your packages updated, and use tools that can alert you to known vulnerabilities.
