Malicious Code Injection in verify-tactiva-mechanical Package
Summary
MAL-2025-170465: Malicious code in verify-tactiva-mechanical (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-tactiva-mechanical package is part of the npm ecosystem, typically used in JavaScript applications. It is designed to facilitate certain functionalities within applications but has been compromised as part of a broader malicious campaign targeting npm packages. This package has been identified as containing scripts that manipulate its own metadata and publish variants to inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which can pollute the npm registry and potentially introduce security risks into applications that depend on this package. The malicious code is designed to exploit the npm ecosystem by creating derivative packages that can mislead developers and users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-tactiva-mechanicalIf 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-tactiva-mechanical package altogether. If your application depends on it, consider replacing it with a trusted alternative package that provides similar functionality without the associated risks.
Conclusion
The verify-tactiva-mechanical package has been identified as containing malicious code that can compromise applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.
See every vulnerability recorded for verify-tactiva-mechanical →
FAQ
It is an npm package that has been compromised and is part of a malicious campaign aimed at manipulating npm's package registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the verify-tactiva-mechanical package from your project and look for a secure alternative.
Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
