Malicious Code Injection in hamzafahim Package: A Threat to npm Users
Summary
MAL-2025-171290: Malicious code in hamzafahim (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 hamzafahim 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 sharing of code among developers. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for users who inadvertently install it.
Vulnerability Detail
The vulnerability in the hamzafahim package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hamzafahimIf 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 hamzafahim package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The hamzafahim package poses a significant threat to developers using npm due to its malicious code designed to manipulate package metadata and publish harmful variants. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for hamzafahim →
FAQ
The hamzafahim package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with harmful code.
If you have the hamzafahim package installed, your application may be at risk of exploitation due to the malicious code that modifies your package.json and publishes harmful variants.
You should immediately uninstall the hamzafahim package using npm uninstall hamzafahim and check your project for any other compromised packages.
You can use Vulert, which allows you to monitor and alert 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 requiring any signup.
