Malicious Code Injection in panicky_falcon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-89351: Malicious code in panicky_falcon_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_falcon_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in 'panicky_falcon_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, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall panicky_falcon_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 'panicky_falcon_z3n' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks.
Conclusion
The 'panicky_falcon_z3n' package poses a significant risk to the npm ecosystem due to its malicious code. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Removing this package and any associated malicious packages is crucial for maintaining project integrity.
See every vulnerability recorded for panicky_falcon_z3n →
FAQ
'panicky_falcon_z3n' is an npm package that has been identified as malicious due to its involvement in a token reward campaign that floods the npm registry with harmful packages.
Using 'panicky_falcon_z3n' can compromise your project's integrity, lead to the introduction of malicious code, and potentially harm your reputation as a developer.
You should immediately remove 'panicky_falcon_z3n' from your project and audit your dependencies to ensure no other malicious packages are present.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
