Malicious Code Injection in akifzaheer Package: npm Vulnerability Overview
Summary
MAL-2025-170774: Malicious code in akifzaheer (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 akifzaheer package is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be associated with a token reward campaign that has led to the proliferation of malicious packages in the npm registry. The primary function of akifzaheer is to provide developers with tools and libraries, but it has been compromised to serve malicious purposes.
Vulnerability Detail
The vulnerability in the akifzaheer package originates from its involvement in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to potential security risks such as the pollution of the npm registry and the introduction of untrusted code into projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall akifzaheerIf 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 akifzaheer package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, regularly audit your project's dependencies to identify and remove any malicious packages.
Conclusion
The akifzaheer package has been identified as containing malicious code that poses significant risks to developers and their projects. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for akifzaheer →
FAQ
The akifzaheer package is an npm package that has been compromised to include malicious code aimed at inflating developer reputation scores through the creation of derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected.
The risks include the introduction of untrusted code into your project, potential data breaches, and the pollution of the npm registry with malicious packages.
Regularly audit your dependencies, use trusted sources for packages, and consider employing automated tools like Vulert to monitor for vulnerabilities.
Remove the akifzaheer package from your project immediately and replace it with a secure alternative. Ensure to audit your project for any other potentially malicious dependencies.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
