Malicious Code Injection in verify-ayca-ama Package
Summary
MAL-2025-170363: Malicious code in verify-ayca-ama (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-ama package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as a component of a broader malicious campaign that aims to exploit npm's package management system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the verify-ayca-ama package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayca-amaIf 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 verify-ayca-ama package and review your project's dependencies for any other potentially compromised packages. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The verify-ayca-ama package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for verify-ayca-ama →
FAQ
The verify-ayca-ama package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.
You should uninstall the verify-ayca-ama package immediately and check for any dependencies that may be affected.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
