Malicious Code Injection in verify-ain-aiusamaki Package
Summary
MAL-2025-170289: Malicious code in verify-ain-aiusamaki (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 verify-ain-aiusamaki 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 packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the verify-ain-aiusamaki package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby compromising the integrity of the npm registry and potentially leading to security risks for developers who unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ain-aiusamakiIf 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 measure, you can avoid using the verify-ain-aiusamaki package and any other packages that are part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The verify-ain-aiusamaki package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for verify-ain-aiusamaki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using this package can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should uninstall the package immediately and audit your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
