Malicious Code Injection in verify-taic-alusakilamu Package
Summary
MAL-2025-170471: Malicious code in verify-taic-alusakilamu (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-taic-alusakilamu 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, leading to significant security risks for developers who may inadvertently use it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the verify-taic-alusakilamu package. This package is linked to a broader scheme that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to pollution of the npm registry and potential security breaches in applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-taic-alusakilamuIf 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-taic-alusakilamu package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The verify-taic-alusakilamu package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain security in open-source projects.
See every vulnerability recorded for verify-taic-alusakilamu →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
If your application uses this package, it may be at risk of security breaches due to the malicious code that alters package metadata and republishing behavior.
You should immediately uninstall the package using npm uninstall verify-taic-alusakilamu and check your application for any potential security issues.
Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
