Malicious Code Injection in poor_pinniped_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95932: Malicious code in poor_pinniped_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 'poor_pinniped_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly integrate these malicious packages into their projects.
Vulnerability Detail
The vulnerability in 'poor_pinniped_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to detect the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall poor_pinniped_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 avoid using the 'poor_pinniped_z3n' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included.
Conclusion
The 'poor_pinniped_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for poor_pinniped_z3n →
FAQ
Using this package can lead to your application being compromised, as it may introduce malicious code that alters your project's dependencies and affects its functionality.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. Vulert provides real-time alerts for open-source vulnerabilities.
Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that check for vulnerabilities in your project.
Immediately uninstall the package using 'npm uninstall poor_pinniped_z3n' and review your project's dependencies for any other potentially malicious packages.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
