Malicious Code Injection in efp9 Package: npm Vulnerability Overview
Summary
MAL-2025-171134: Malicious code in efp9 (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 efp9 package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the efp9 package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall efp9If 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 prevent the installation of the efp9 package by adding it to your project's package.json file under 'devDependencies' or by using npm's 'no-optional' flag during installation. Example command: npm install efp9 --no-optional.
Conclusion
The efp9 package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help you stay ahead of potential vulnerabilities in your software.
See every vulnerability recorded for efp9 →
FAQ
The efp9 package is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially damaging your reputation.
If you have installed efp9, you should update it to the latest patched version or remove it from your project to mitigate the risk.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.
