Malicious Code Injection in verify-aya-aul Package
Summary
MAL-2025-170340: Malicious code in verify-aya-aul (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The verify-aya-aul 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 for token rewards in the tea.xyz protocol. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the verify-aya-aul package stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish itself, leading to pollution of the npm registry. The origin of this vulnerability can be traced back to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and distribution of these harmful packages. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently expose their projects to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-aya-aulIf 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-aya-aul 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 address vulnerabilities in your project.
Conclusion
The verify-aya-aul package poses a significant risk due to its malicious code that alters package files and repopulates the npm registry with harmful variants. It is essential for developers to remove this package and regularly audit their dependencies to maintain the security of their projects. Utilizing tools like Vulert can further enhance your ability to monitor for vulnerabilities in real-time.
See every vulnerability recorded for verify-aya-aul →
FAQ
The verify-aya-aul package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with harmful derivatives.
The malicious code modifies your package.json file, removes private flags, and allows the package to republish itself under different names, potentially compromising your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check if your application is affected by this vulnerability.
Remove the verify-aya-aul package from your project, regularly audit your dependencies, and ensure you are using updated and secure versions of your packages.
Yes, regularly monitor your dependencies, use tools like npm audit, and consider using services like Vulert to stay informed about vulnerabilities in your open-source packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
