Malicious Code Injection in verify-ayca-amalua Package
Summary
MAL-2025-170368: Malicious code in verify-ayca-amalua (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-ayca-amalua package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the verify-ayca-amalua package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The malicious payload can lead to the proliferation of insecure packages, potentially affecting applications that rely on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayca-amaluaIf 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 avoid using the verify-ayca-amalua package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert to receive real-time alerts for vulnerabilities.
Conclusion
The verify-ayca-amalua package poses a significant security risk due to its malicious behavior. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for verify-ayca-amalua →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the inclusion of insecure packages in your application, potentially compromising its security.
You should remove the verify-ayca-amalua package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file to alert you of any 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 an account.
