Malicious Code Injection in conservative_warbler_z3n: A Threat to npm Packages
Summary
MAL-2025-93737: Malicious code in conservative_warbler_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 'conservative_warbler_z3n' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.
Vulnerability Detail
The vulnerability in 'conservative_warbler_z3n' stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This results in a continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the broader trend of malicious npm packages that exploit the registry for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conservative_warbler_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 'conservative_warbler_z3n' package and any other packages that appear to be part of the tea.xyz campaign. Regularly audit your dependencies to ensure they do not include malicious packages.
Conclusion
The 'conservative_warbler_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for similar threats. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for conservative_warbler_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should immediately remove the package from your project and audit your dependencies to ensure no other malicious packages are present.
As of now, there are no known patched versions. It is best to remove the package entirely until a secure version is released.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
