Malicious Code Injection in abigailscott Package - npm Vulnerability
Summary
MAL-2025-170641: Malicious code in abigailscott (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 abigailscott package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often leveraged by developers to enhance their projects with additional functionalities. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to significant security risks for users.
Vulnerability Detail
The vulnerability in the abigailscott package stems from its involvement in the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative packages with randomized names, modifying the package.json file to remove private flags and changing version numbers. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abigailscottIf 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 abigailscott package and replace it with a similar package that does not have known vulnerabilities. Additionally, regularly audit your dependencies using 'npm audit' to identify and address potential security issues.
Conclusion
The abigailscott package poses a significant security risk due to its involvement in a malicious npm campaign. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for abigailscott →
FAQ
The abigailscott package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if it relies on affected packages.
You should uninstall the abigailscott package immediately and check your project for any dependencies that may have been affected.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without 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.
