Malicious Code Injection in grumpy_blackbird_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-94773: Malicious code in grumpy_blackbird_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 'grumpy_blackbird_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior compromises the integrity of the npm registry and poses risks to developers who unknowingly use these packages.
Vulnerability Detail
The vulnerability in 'grumpy_blackbird_z3n' originates from its association with the tea.xyz token reward campaign. The package contains scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This malicious activity leads to the continuous republishing of variants, which pollutes the npm registry and can mislead developers into using compromised packages. The ramifications include potential security breaches, loss of trust in the npm ecosystem, and the risk of integrating malicious code into legitimate applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grumpy_blackbird_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 'grumpy_blackbird_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like 'npm audit'.
Conclusion
The 'grumpy_blackbird_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant and regularly audit their dependencies to mitigate risks associated with such vulnerabilities. Removing compromised packages and utilizing tools like Vulert can help maintain the integrity of your software projects.
See every vulnerability recorded for grumpy_blackbird_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and repackages itself under random names, leading to pollution of the npm registry.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed 'grumpy_blackbird_z3n', you should uninstall it immediately using 'npm uninstall grumpy_blackbird_z3n' and check for any other affected packages.
Yes, tools like 'npm audit' can help you identify vulnerabilities in your npm packages, and platforms like Vulert can provide real-time monitoring.
Using compromised packages can lead to security breaches, data loss, and the introduction of malicious code into your applications, which can harm users and damage your reputation.
