Malicious Code Injection in blind_chicken-appteadev Package

blind_chicken-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100006: Malicious code in blind_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 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 blind_chicken-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate development tasks but has been compromised by malicious actors. This package is linked to a broader campaign that exploits npm's publishing mechanisms to inflate developer reputations through automated scripts.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the blind_chicken-appteadev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby polluting the npm registry and potentially leading to security risks for applications relying on this package. The malicious code is part of a larger scheme associated with the tea.xyz token reward campaign.

How To Fix

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

npm uninstall blind_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 workaround, you can remove the blind_chicken-appteadev package from your project by executing: npm uninstall blind_chicken-appteadev. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The blind_chicken-appteadev package has been identified as containing malicious code that poses significant risks to applications using it. It is crucial to take immediate action by updating or removing the package to ensure the security of your project.

See every vulnerability recorded for blind_chicken-appteadev →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file and may expose your application to further security risks.

You should immediately update or uninstall the package to mitigate any potential risks.

Yes, you can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

You can use the Vulert playground at Vulert Scanner to check your application without needing to sign up.

How To Fix

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

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