Malicious Code Injection in crude_bird-strongdev Package
Summary
MAL-2025-101108: Malicious code in crude_bird-strongdev (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 crude_bird-strongdev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package, like others in the campaign, is designed to automatically publish derivative packages with altered metadata, which can lead to significant issues in the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the crude_bird-strongdev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to a broader campaign that exploits npm for token rewards, making it a significant concern for developers relying on this ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall crude_bird-strongdevIf 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 crude_bird-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file to identify any potentially malicious packages.
Conclusion
The crude_bird-strongdev package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for crude_bird-strongdev →
FAQ
The crude_bird-strongdev package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the crude_bird-strongdev package, you should uninstall it immediately using the command npm uninstall crude_bird-strongdev.
Yes, consider looking for other npm packages that offer similar functionalities without the associated risks of malicious code.
