Malicious Code Injection in binding_magpie-appteadev Package
Summary
MAL-2025-99979: Malicious code in binding_magpie-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 binding_magpie-appteadev package is part of the npm ecosystem, often utilized 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 developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the binding_magpie-appteadev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious scripts (auto.js, autopublish.js, etc.) are designed to continuously republish these variants, potentially compromising the integrity of the npm ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall binding_magpie-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 measure, you can avoid using the binding_magpie-appteadev package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The binding_magpie-appteadev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for binding_magpie-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the binding_magpie-appteadev package immediately and check your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
