Malicious Code Injection in aamirhafiz Package: npm Vulnerability Overview
Summary
MAL-2025-170610: Malicious code in aamirhafiz (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 aamirhafiz package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These malicious packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants of the original package, often with altered metadata.
Vulnerability Detail
The vulnerability originates from the aamirhafiz package being associated with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of projects relying on these packages. The malicious payload can potentially affect any project that inadvertently includes this package, leading to security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aamirhafizIf 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 aamirhafiz package altogether. If it is a dependency of another package, consider using alternative packages that do not have known vulnerabilities. You can also lock your dependencies using package-lock.json to prevent automatic updates to vulnerable packages.
Conclusion
The aamirhafiz package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for aamirhafiz →
FAQ
The aamirhafiz package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should remove the aamirhafiz package from your project immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts 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 needing to sign up.
