Malicious Code Injection in injured_beetle-appteadev Package

injured_beetle-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104207: Malicious code in injured_beetle-appteadev (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The injured_beetle-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm environment, but it has been compromised to include malicious code that affects its integrity and security. The package is known for generating and publishing derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability in the injured_beetle-appteadev 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 behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The malicious payload is designed to continuously republish variants, thereby increasing the potential for exploitation and misuse.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall injured_beetle-appteadev

If 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 injured_beetle-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project using tools like Vulert, which can alert you to any vulnerabilities in your dependencies.

Conclusion

The injured_beetle-appteadev package has been identified as containing malicious code that compromises its integrity and poses risks to developers. It is crucial to uninstall this package and monitor your project for vulnerabilities using tools like Vulert. Stay informed about updates and patches to maintain the security of your applications.

See every vulnerability recorded for injured_beetle-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate various functionalities but compromised with malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, potentially leading to security vulnerabilities and reputation issues.

You should uninstall the injured_beetle-appteadev package immediately and monitor your project for any further vulnerabilities.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall injured_beetle-appteadev

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback