Malicious Code Injection in verify-ain-ukasiam Package
Summary
MAL-2025-170309: Malicious code in verify-ain-ukasiam (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The verify-ain-ukasiam package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in the verify-ain-ukasiam package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of 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 compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ain-ukasiamIf 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, you can avoid using the verify-ain-ukasiam package altogether. If it is already part of your project, consider replacing it with a similar package that does not exhibit malicious behavior. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The verify-ain-ukasiam package poses a significant risk due to its malicious code that alters package metadata and can lead to the pollution of the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for verify-ain-ukasiam →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The malicious code modifies your package.json, potentially leading to the use of compromised packages and security vulnerabilities in your application.
You should uninstall the verify-ain-ukasiam package immediately and check for any dependencies that may be affected.
Yes, regularly monitor your dependencies using tools like Vulert to receive real-time alerts for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
