Malicious Code Injection in verify-tactiva-mec Package
Summary
MAL-2025-170461: Malicious code in verify-tactiva-mec (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-mec package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish numerous derivative versions to inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may contain further vulnerabilities or malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-tactiva-mecIf 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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which analyzes your package-lock.json file to detect vulnerabilities in real-time.
Conclusion
The verify-tactiva-mec package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for verify-tactiva-mec →
FAQ
The verify-tactiva-mec package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code can compromise your project's integrity by introducing vulnerabilities and potentially harmful behavior through modified package versions.
You should remove the verify-tactiva-mec package from your project and consider using alternative packages that are secure.
You can use Vulert, which allows you to monitor your project's dependencies by analyzing the package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
