Malicious Code Injection in energetic_bee-appteadev: A Threat to npm Users
Summary
MAL-2025-102096: Malicious code in energetic_bee-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 package 'energetic_bee-appteadev' is part of the npm ecosystem and is associated with 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, leading to significant security concerns.
Vulnerability Detail
The vulnerability in 'energetic_bee-appteadev' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The malicious code is part of a broader trend of malicious npm packages that exploit the ecosystem for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall energetic_bee-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 prevent the package from being installed by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help mitigate the risk until a proper fix is implemented.
Conclusion
The 'energetic_bee-appteadev' package poses a significant threat due to its malicious code that alters package configurations and republish variants. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for energetic_bee-appteadev →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.
You should uninstall the package immediately using 'npm uninstall energetic_bee-appteadev' and check for any other affected packages.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Failing to address this vulnerability could lead to your application being compromised, exposing sensitive data, or damaging your reputation as a developer.
