Malicious Code Injection in panicky_jay_z3n: A Threat to npm Packages
Summary
MAL-2025-95830: Malicious code in panicky_jay_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 panicky_jay_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in panicky_jay_z3n stems from its association with a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, potentially leading to security risks for developers who unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall panicky_jay_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 panicky_jay_z3n package until a fixed version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The panicky_jay_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers are advised to update their packages and consider using tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for panicky_jay_z3n →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you are using panicky_jay_z3n, you should update to the latest patched version or consider removing it from your project until a fix is available.
Using this vulnerable package can lead to security risks, including the exposure of sensitive information and the potential for your application to be compromised.
Vulert uses your package-lock.json file to monitor and alert you in real-time about open-source vulnerabilities, helping you maintain the security of your software.
