Malicious Code Injection in verify-ayai-galaka Package
Summary
MAL-2025-170351: Malicious code in verify-ayai-galaka (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-ayai-galaka 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 exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and compromise their projects.
Vulnerability Detail
The vulnerability in the verify-ayai-galaka package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alter version numbers. This allows the package to generate random names and continuously republish itself, polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly integrate this package into their projects, leading to reputation damage and possible exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayai-galakaIf 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-ayai-galaka package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package-lock.json file to ensure no malicious packages are included. You can also use tools like Vulert to monitor your project for vulnerabilities without requiring code access.
Conclusion
The verify-ayai-galaka package poses a significant risk due to its malicious nature and association with a broader campaign to exploit the npm registry. Developers should take immediate action to remove this package and monitor their projects for potential vulnerabilities.
See every vulnerability recorded for verify-ayai-galaka →
FAQ
The verify-ayai-galaka package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise your project's security if the malicious package is integrated.
Remove the verify-ayai-galaka package and regularly audit your dependencies. Use tools like Vulert to monitor for vulnerabilities.
Currently, there is no patched version of the verify-ayai-galaka package. The best course of action is to uninstall it.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
