Malicious Code Injection in original_mackerel-toolteadev Package
Summary
MAL-2025-106796: Malicious code in original_mackerel-toolteadev (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 original_mackerel-toolteadev package is part of the npm ecosystem, designed for developers to integrate with Mackerel, a server monitoring service. This package, like many others, is intended to facilitate the management and monitoring of server health and performance. However, it has been compromised, making it susceptible to malicious activities that can affect developers and their projects.
Vulnerability Detail
The vulnerability stems from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can inflate developer reputation scores fraudulently. The malicious payload can potentially expose users to security risks and degrade the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall original_mackerel-toolteadevIf 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 remove the original_mackerel-toolteadev package from your project by executing the command: npm uninstall original_mackerel-toolteadev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The original_mackerel-toolteadev package has been compromised with malicious code that can affect developers and their projects. It is essential to take immediate action to update or remove the package to safeguard your applications. Utilizing tools like Vulert can help in monitoring and alerting for such vulnerabilities in real-time.
See every vulnerability recorded for original_mackerel-toolteadev →
FAQ
The malicious code originates from a campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application using the Vulert playground without any signup.
Using the compromised package can lead to security vulnerabilities, including unauthorized access to your project and the potential for malicious code execution.
Regularly updating your dependencies, using tools like Vulert for monitoring, and reviewing package sources can help mitigate the risk of vulnerabilities.
Immediately remove the package and monitor your application for any unusual behavior. Update to a secure version as soon as it is available.
