Malicious Code Injection in verify-ayicaku-amuinaha Package
Summary
MAL-2025-170411: Malicious code in verify-ayicaku-amuinaha (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-ayicaku-amuinaha package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a larger scheme involving the tea.xyz token reward campaign, which has led to the proliferation of malicious packages in the npm registry. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages.
Vulnerability Detail
The vulnerability in the verify-ayicaku-amuinaha package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayicaku-amuinahaIf 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-ayicaku-amuinaha package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The verify-ayicaku-amuinaha package contains malicious code that poses significant risks to developers and the npm ecosystem. It is essential to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the security of your applications.
See every vulnerability recorded for verify-ayicaku-amuinaha →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
Using this package can lead to security risks, including the potential for your project to be compromised or polluted with unwanted packages.
You should uninstall the package immediately using the command npm uninstall verify-ayicaku-amuinaha.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
