Malicious Code Injection in aamirhakeem Package: npm Vulnerability Summary
Summary
MAL-2025-170611: Malicious code in aamirhakeem (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 aamirhakeem package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a larger campaign that aims to exploit the npm registry by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues within the ecosystem.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the aamirhakeem package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The scripts included in the package (such as auto.js and autopublish.js) are designed to continuously republish variants of the package, polluting the npm registry and potentially compromising other projects that depend on it. The ramifications include a loss of trust in the npm ecosystem, potential security risks for developers, and the degradation of the quality of available packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aamirhakeemIf 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 aamirhakeem package and consider replacing it with a similar, trusted package. Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring code access or installation.
Conclusion
The aamirhakeem package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for aamirhakeem →
FAQ
The aamirhakeem package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity.
You should uninstall the package immediately using the command npm uninstall aamirhakeem and check your project for any other vulnerabilities.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing 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 signing up.
