Malicious Code Injection in abigailfoster Package: npm Vulnerability Overview
Summary
MAL-2025-170640: Malicious code in abigailfoster (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 abigailfoster package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. Its primary functionality is to serve as a dependency for JavaScript applications, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the abigailfoster package originates from its involvement in the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abigailfosterIf 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 abigailfoster package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The abigailfoster package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies regularly to maintain the security of your applications.
See every vulnerability recorded for abigailfoster →
FAQ
The abigailfoster package is an npm package that has been compromised to include malicious code as part of a broader attack on the npm ecosystem.
If your project uses the abigailfoster package, it may be at risk of having its package metadata altered, leading to potential security issues and pollution of the npm registry.
You should immediately uninstall the abigailfoster package using npm uninstall abigailfoster and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.
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.
