Malicious Code Injection in continued_alpaca-notthedevs Package
Summary
MAL-2025-100931: Malicious code in continued_alpaca-notthedevs (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 continued_alpaca-notthedevs package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various functionalities within applications. 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 poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that floods npm with malicious packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall continued_alpaca-notthedevsIf 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 continued_alpaca-notthedevs package entirely and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The continued_alpaca-notthedevs package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects to maintain the integrity and security of their applications.
See every vulnerability recorded for continued_alpaca-notthedevs →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
Using this package can lead to security risks, including the potential for your project to be compromised or polluted with malicious code.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
