Malicious Code Detected in Protective Beige Falcon Package - npm Vulnerability

protective-beige-falcon Updated 25 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-138949: Malicious code in protective-beige-falcon (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 'protective-beige-falcon' package 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 identified as containing malicious code that alters package metadata and publishes harmful variants.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the 'protective-beige-falcon' package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of other packages. This behavior can lead to security risks for developers who unknowingly integrate these malicious packages into their projects.

How To Fix

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

npm uninstall protective-beige-falcon

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, avoid using the 'protective-beige-falcon' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.

Conclusion

The 'protective-beige-falcon' package has been identified as containing malicious code that poses a significant risk to developers. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for protective-beige-falcon →

Share this vulnerability

FAQ

It is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially compromising your project's security.

You should uninstall the 'protective-beige-falcon' package immediately using 'npm uninstall protective-beige-falcon'.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall protective-beige-falcon

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