Malicious Code Injection in verify-tactiva-m Package
Summary
MAL-2025-170459: Malicious code in verify-tactiva-m (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-m package is part of the npm ecosystem, often utilized in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system to inflate developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in the verify-tactiva-m package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially expose users to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-tactiva-mIf 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-m package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json does not include any references to this malicious package.
Conclusion
The verify-tactiva-m package contains malicious code that poses a significant risk to the npm ecosystem and its users. It is crucial to remove this package from your projects and stay vigilant about the packages you use. Utilizing tools like Vulert can help you monitor for vulnerabilities effectively.
See every vulnerability recorded for verify-tactiva-m →
FAQ
The verify-tactiva-m package is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm's publishing system.
The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks, including the potential for malicious code execution.
If you have installed the verify-tactiva-m package, you should uninstall it immediately using the command npm uninstall verify-tactiva-m.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor your projects for vulnerabilities.
