Malicious Code Injection in alyssadavis Package: npm Vulnerability Overview
Summary
MAL-2025-170796: Malicious code in alyssadavis (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 alyssadavis package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish variants of the original package, potentially leading to security risks for users who inadvertently install them.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the alyssadavis package, which is associated with the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses significant risks, including the potential for unauthorized access to sensitive data and the compromise of user systems through the installation of these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alyssadavisIf 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 alyssadavis package and instead 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 alyssadavis package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for alyssadavis →
FAQ
The alyssadavis package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the installation of malicious code that compromises your application's security, potentially exposing sensitive data and allowing unauthorized access.
You should immediately uninstall the alyssadavis package using the command npm uninstall alyssadavis and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application using the Vulert playground at Vulert Scanner.
Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always ensure to review the package's reputation and security history before installation.
