Malicious Code Injection in verify-taic-malaskkulu Package
Summary
MAL-2025-170484: Malicious code in verify-taic-malaskkulu (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-malaskkulu 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 process by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the verify-taic-malaskkulu package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to security risks for developers who unknowingly incorporate these compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-taic-malaskkuluIf 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-malaskkulu package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. You can do this by running the following command: npm uninstall verify-taic-malaskkulu.
Conclusion
The verify-taic-malaskkulu package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for verify-taic-malaskkulu →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
Incorporating this package can lead to security risks, including the potential for your project to be associated with malicious activities.
You should immediately uninstall the verify-taic-malaskkulu package from your project and check for any alternative packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
