Malicious Code Injection in hasibaftab Package: A Threat to npm Ecosystem
Summary
MAL-2025-171297: Malicious code in hasibaftab (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 hasibaftab package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry.
Vulnerability Detail
The vulnerability in the hasibaftab package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards in the tea protocol, leading to potential pollution of the npm registry and compromising the security of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hasibaftabIf 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, avoid using the hasibaftab package and any packages that depend on it. Regularly audit your project's dependencies using 'npm audit' to identify and address any vulnerabilities.
Conclusion
The hasibaftab package poses a significant risk to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for hasibaftab →
FAQ
The hasibaftab package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of your application.
You should uninstall the hasibaftab package immediately using 'npm uninstall hasibaftab' and check for any dependent packages.
Yes, 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.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
