Malicious Code Injection in retail_boa_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96341: Malicious code in retail_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 package 'retail_boa_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'retail_boa_z3n' originates from its association with malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by inflating reputation scores fraudulently and may introduce security risks into applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall retail_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 workaround, you can avoid using the 'retail_boa_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'retail_boa_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for retail_boa_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages it under random names, leading to npm registry pollution.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall retail_boa_z3n' and review your dependencies for any other potentially malicious packages.
Yes, the impacts include the potential for reputation score inflation among developers and the introduction of security risks into applications that depend on compromised packages.
Regularly audit your dependencies, use trusted sources, and leverage tools like Vulert to monitor for vulnerabilities in your open-source packages.
