Malicious Code Injection in Protestant Falcon Requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96082: Malicious code in protestant_falcon_requirement (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 'protestant_falcon_requirement' package is part of the npm ecosystem, often utilized for various JavaScript applications. This package has been identified as part of a broader malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with the intent of inflating developer reputation scores for token rewards associated with the tea.xyz protocol.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'protestant_falcon_requirement' package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this vulnerability is linked to a campaign that floods npm with such malicious packages, making it crucial for developers to be vigilant.

How To Fix

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

npm uninstall protestant_falcon_requirement

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 'protestant_falcon_requirement' package from your project until a secure version is released. You can do this by executing the following command: npm uninstall protestant_falcon_requirement. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'protestant_falcon_requirement' package has been identified as containing malicious code that poses a significant risk to applications using it. Developers are urged to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for protestant_falcon_requirement →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and republishes variants to the npm registry, potentially compromising applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file. Visit Vulert Scanner to check your application without any signup.

If immediate updates are not possible, consider removing the package from your project and using alternative solutions until a secure version is available.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages or through security advisories related to npm.

How To Fix

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

npm uninstall protestant_falcon_requirement

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