Malicious Code Injection in ameerzaid Package: npm Vulnerability Overview
Summary
MAL-2025-170820: Malicious code in ameerzaid (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 ameerzaid 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 deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in the ameerzaid 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 leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious code is designed to exploit the npm platform for token rewards, posing a significant risk to developers and users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ameerzaidIf 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 workaround, you can temporarily avoid using the ameerzaid package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to the package.json file.
Conclusion
The ameerzaid package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and users. It is essential to take immediate action to remove this package and monitor for any other vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for ameerzaid →
FAQ
The ameerzaid package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
This vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising its security and integrity.
You should uninstall the ameerzaid package immediately and check your project for any other potentially malicious packages.
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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
