Malicious Code Injection in verify-ayca-amilsukami Package
Summary
MAL-2025-170377: Malicious code in verify-ayca-amilsukami (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-amilsukami package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package, like others in the campaign, is to manipulate npm's publishing system to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the verify-ayca-amilsukami package. This code is designed to modify 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 inadvertently use these packages. The ramifications include compromised project integrity and exposure to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayca-amilsukamiIf 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-amilsukami package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The verify-ayca-amilsukami package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and informed is key to maintaining the security of your applications.
See every vulnerability recorded for verify-ayca-amilsukami →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its integrity and exposing it to further security risks.
You should uninstall the verify-ayca-amilsukami package immediately and monitor your project for any unusual behavior.
Regularly audit your dependencies, use tools like Vulert for real-time vulnerability monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
