Malicious Code Injection in great_alpaca-silentdev Package
Summary
MAL-2025-103367: Malicious code in great_alpaca-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 great_alpaca-silentdev package is part of the npm ecosystem, primarily used for various development purposes. 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 package metadata and inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the package's involvement in the tea.xyz token reward campaign, which has led to the creation of numerous malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants pollutes the npm registry, posing risks such as unauthorized access to sensitive data and potential exploitation of affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall great_alpaca-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 workaround, you can remove the great_alpaca-silentdev package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall great_alpaca-silentdev.
Conclusion
The great_alpaca-silentdev package has been compromised, posing significant risks to applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for great_alpaca-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package metadata, potentially exposing your application to further risks.
Check the npm registry for any updated versions of the great_alpaca-silentdev package that address this vulnerability.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
Consider removing the package from your project as a temporary measure until a secure version is available.
