Malicious Code Injection in established_chicken-appteadev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102246: Malicious code in established_chicken-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The established_chicken-appteadev package is part of the npm ecosystem, commonly used for various JavaScript applications. This package has been identified as part of a token reward campaign that exploits npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the established_chicken-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a compromised npm registry and potential security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such harmful packages.

How To Fix

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

npm uninstall established_chicken-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 measure, you can remove the established_chicken-appteadev package from your project until a secure version is released. You can do this by executing the following command: npm uninstall established_chicken-appteadev. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. Vulert uses the package-lock.json file to alert you in real-time about any open-source vulnerabilities in your software.

Conclusion

The established_chicken-appteadev package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to stay informed about such vulnerabilities, regularly update their packages, and utilize monitoring tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for established_chicken-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately and monitor your project for any signs of compromise.

Regularly update your dependencies, use tools like Vulert for monitoring, and review packages before installation.

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

How To Fix

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

npm uninstall established_chicken-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