Malicious Code Injection in verify-ayica-amuinadabuhua Package
Summary
MAL-2025-170401: Malicious code in verify-ayica-amuinadabuhua (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-ayica-amuinadabuhua 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the verify-ayica-amuinadabuhua 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 is designed to pollute the npm registry and can lead to the unintended installation of compromised packages by developers, potentially exposing their applications to further vulnerabilities and malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayica-amuinadabuhuaIf 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 verify-ayica-amuinadabuhua package and any other packages that may be part of the malicious campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The verify-ayica-amuinadabuhua package poses a significant security risk due to its malicious code injection. It is essential for developers to be vigilant and regularly audit their dependencies to protect their applications from such vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for verify-ayica-amuinadabuhua →
FAQ
It 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 installation of compromised packages, potentially exposing your application to security risks.
You should uninstall the package immediately and update your project dependencies to ensure security.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring an account.
