Malicious Code Injection in potential_mackerel-appteadev Package
Summary
MAL-2025-107167: Malicious code in potential_mackerel-appteadev (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 potential_mackerel-appteadev package is part of the npm ecosystem, primarily used for developing applications in JavaScript. It is designed to facilitate various functionalities within the Node.js environment. However, this package has been identified as part of a malicious campaign that aims to exploit npm's package management system, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability arises from the malicious code embedded in the potential_mackerel-appteadev package. This package is linked to the tea.xyz token reward campaign, which has been known to flood npm with harmful packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores fraudulently but also leads to the pollution of the npm registry with derivative packages, potentially compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_mackerel-appteadevIf 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 potential_mackerel-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. 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 potential_mackerel-appteadev package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain a secure development environment.
See every vulnerability recorded for potential_mackerel-appteadev →
FAQ
It is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application.
You should uninstall the package immediately and check for any alternative packages that are safe to use.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
