Malicious Code Injection in jbeeec-devapptea Package
Summary
MAL-2025-104527: Malicious code in jbeeec-devapptea (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 jbeeec-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses significant risks to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability in the jbeeec-devapptea package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks and loss of trust in the affected packages. The malicious payload is designed to inflate developer reputation scores for token rewards, making it a significant concern for the npm community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jbeeec-devappteaIf 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 jbeeec-devapptea package by using the following command to uninstall it: npm uninstall jbeeec-devapptea. Additionally, consider using npm audit to identify and address other potential vulnerabilities in your project.
Conclusion
The jbeeec-devapptea package is associated with a malicious campaign that poses significant risks to the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take appropriate actions to remove affected packages, and utilize tools to monitor their projects for security issues.
See every vulnerability recorded for jbeeec-devapptea →
FAQ
The jbeeec-devapptea package is part of a malicious campaign that floods the npm registry with derivative packages designed to manipulate developer reputation scores.
This vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and affecting the integrity of your project dependencies.
You should uninstall the jbeeec-devapptea package immediately and monitor your project for any other vulnerabilities using tools like npm audit.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.
Regularly audit your dependencies using npm audit, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
