Malicious Code Injection in abufahim Package: npm Vulnerability Overview
Summary
MAL-2025-170643: Malicious code in abufahim (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 abufahim package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications for its ease of integration and functionality. 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 vulnerability poses significant risks to developers and users alike, as it can lead to the proliferation of harmful code within the npm registry.
Vulnerability Detail
The vulnerability in the abufahim package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also exposes users to potential security risks, as the malicious payload can lead to the installation of harmful dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abufahimIf 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 abufahim 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 project.
Conclusion
The abufahim package poses a significant security risk due to its association with a malicious campaign aimed at manipulating the npm registry. It is essential for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for abufahim →
FAQ
The abufahim package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the installation of malicious code, which may compromise the security and integrity of your application.
You should remove the abufahim package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
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.
