Malicious Code Injection in pale_boa_z3n: npm Package Vulnerability
Summary
MAL-2025-122437: Malicious code in pale_boa_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 pale_boa_z3n package 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 deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability in pale_boa_z3n originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative versions with altered metadata, including the removal of private flags and randomization of package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to code injection and other security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pale_boa_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, avoid using the pale_boa_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any updates or vulnerabilities.
Conclusion
The pale_boa_z3n package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your applications from potential threats.
See every vulnerability recorded for pale_boa_z3n →
FAQ
pale_boa_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry, aimed at inflating developer reputation scores.
If your application uses the pale_boa_z3n package, it may be at risk of code injection and other security issues due to the malicious scripts embedded within the package.
You should uninstall the pale_boa_z3n package immediately and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using well-established and trusted packages that provide similar functionality. Always verify the source and reputation of packages before installation.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.