Malicious Code Injection in weekly_warbler-silentdev Package
Summary
MAL-2025-110797: Malicious code in weekly_warbler-silentdev (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 weekly_warbler-silentdev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing of variants, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential exposure of sensitive data and compromise of the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall weekly_warbler-silentdevIf 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, you can avoid using the weekly_warbler-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The weekly_warbler-silentdev package poses a significant security risk due to its involvement in a malicious campaign that manipulates the npm registry. It is crucial to uninstall this package and monitor your project for vulnerabilities using tools like Vulert to maintain the integrity of your software.
See every vulnerability recorded for weekly_warbler-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the exposure of sensitive data and compromise the integrity of the npm registry, affecting the security of your project.
You should uninstall the weekly_warbler-silentdev package immediately using 'npm uninstall weekly_warbler-silentdev' and look for alternative packages.
Currently, there are no patched versions of the weekly_warbler-silentdev package available.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. Visit Vulert Scanner to check your application.
