Malicious Code Injection in verify-ayca-amilsuka Package
Summary
MAL-2025-170374: Malicious code in verify-ayca-amilsuka (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-amilsuka 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 components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in the verify-ayca-amilsuka package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for developers to unknowingly use compromised packages, which can introduce vulnerabilities into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayca-amilsukaIf 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-amilsuka package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure that no malicious packages are included.
Conclusion
The verify-ayca-amilsuka package poses a significant risk due to its malicious behavior of modifying package files and republishing variants to the npm registry. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.
See every vulnerability recorded for verify-ayca-amilsuka →
FAQ
The verify-ayca-amilsuka package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
If your application uses the verify-ayca-amilsuka package, it may be at risk of incorporating malicious code that could compromise its security and integrity.
You should uninstall the verify-ayca-amilsuka package immediately and check your project for any references to it in your package-lock.json file.
You can use tools like Vulert, which monitors your package-lock.json file 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 needing to sign up.
