Malicious Code Injection in verify-ayicku-amha Package
Summary
MAL-2025-170413: Malicious code in verify-ayicku-amha (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-ayicku-amha package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in the verify-ayicku-amha package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ayicku-amhaIf 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 workaround, you can avoid using the verify-ayicku-amha package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package dependencies for vulnerabilities. Here's how to use Vulert:
- Go to https://vulert.com/scanner.
- Upload your package-lock.json file.
- Review the report for any vulnerabilities, including the one associated with verify-ayicku-amha.
Conclusion
The verify-ayicku-amha package poses significant risks due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your projects.
See every vulnerability recorded for verify-ayicku-amha →
FAQ
The verify-ayicku-amha package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The malicious code modifies your package.json file, removes private flags, and can lead to the proliferation of harmful packages in your project.
You should remove the verify-ayicku-amha package from your project immediately and consider using alternative packages.
You can use Vulert to monitor your package dependencies in real-time by uploading your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
