Malicious Code Injection in alyssawilliams Package: npm Vulnerability Overview
Summary
MAL-2025-170797: Malicious code in alyssawilliams (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The alyssawilliams package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol.
Vulnerability Detail
The vulnerability in the alyssawilliams package originates from its association with a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, which can lead to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alyssawilliamsIf 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 alyssawilliams package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict dependency management practices to monitor and control the packages used in your projects.
Conclusion
The alyssawilliams package poses a significant security risk due to its association with a malicious campaign that exploits the npm registry. Developers are advised to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for alyssawilliams →
FAQ
The alyssawilliams package is a JavaScript package available on npm, which has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should remove the alyssawilliams package from your project immediately and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
