Malicious Code Injection in critical_pinniped_z3n Package
Summary
MAL-2025-93852: Malicious code in critical_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 critical_pinniped_z3n package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through the automatic generation and publication of numerous variants, which can lead to significant issues in the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the critical_pinniped_z3n package, which is associated with the tea.xyz token reward campaign. It includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, thereby polluting the npm registry. This can lead to compromised developer accounts, loss of trust in the npm ecosystem, and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall critical_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 workaround, you can avoid using the critical_pinniped_z3n package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The critical_pinniped_z3n package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for critical_pinniped_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially exposing it to further attacks.
You should uninstall the critical_pinniped_z3n package immediately and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
