Malicious Code Injection in verify-tac-mechanical Package

verify-tac-mechanical Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170445: Malicious code in verify-tac-mechanical (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The verify-tac-mechanical package is part of the npm ecosystem and is typically used for various mechanical verification tasks. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful packages. The malicious code embedded in this package is designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the verify-tac-mechanical 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 leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload can potentially allow attackers to execute arbitrary code or manipulate other packages that depend on this one.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall verify-tac-mechanical

If 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 temporarily avoid using the verify-tac-mechanical package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to detect any vulnerabilities in real-time.

Conclusion

The verify-tac-mechanical package has been identified as containing malicious code that can compromise your application. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for verify-tac-mechanical →

Share this vulnerability

FAQ

The verify-tac-mechanical package is an npm package used for mechanical verification tasks but has been compromised with malicious code.

The malicious code can modify your package metadata, inflate reputation scores, and potentially allow for arbitrary code execution.

You should remove the verify-tac-mechanical package from your project and monitor for any updates or patches.

Yes, you can use the Vulert playground to check your application for vulnerabilities without requiring any installation or signup.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall verify-tac-mechanical

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback