Malicious Code Injection in verify-tactiva-mechanica: A Threat to npm Packages
Summary
MAL-2025-170464: Malicious code in verify-tactiva-mechanica (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-tactiva-mechanica' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious behavior includes modifying package metadata and republishing under various names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability originates from the 'verify-tactiva-mechanica' package, which is linked to a broader malicious campaign targeting npm. The malicious code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also contributes to the pollution of the npm registry, making it difficult for developers to trust the packages they use. The ramifications include potential security breaches, loss of control over package versions, and a degraded developer experience.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-tactiva-mechanicaIf 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-mechanica' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'verify-tactiva-mechanica' package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for verify-tactiva-mechanica →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust packages, and may expose your project to security risks.
You should uninstall the 'verify-tactiva-mechanica' package immediately and monitor your project for any potential vulnerabilities.
Yes, you can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
