Malicious Code Injection in verify-ain-aiusamakli: A Threat to npm Users
Summary
MAL-2025-170291: Malicious code in verify-ain-aiusamakli (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 package 'verify-ain-aiusamakli' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in 'verify-ain-aiusamakli' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to a polluted npm registry. The ramifications include potential security risks for users who unknowingly install these compromised packages, as they may introduce further vulnerabilities or malicious behavior into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ain-aiusamakliIf 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-ain-aiusamakli' package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'verify-ain-aiusamakli' package poses a significant security risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for verify-ain-aiusamakli →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.
If you have installed 'verify-ain-aiusamakli', you should uninstall it immediately using 'npm uninstall verify-ain-aiusamakli' and check for any other compromised packages.
Yes, consider using other npm packages that provide similar functionality but do not have known vulnerabilities.
Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
