Malicious Code Injection in possible_falcon_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107158: Malicious code in possible_falcon_replicate_automation (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The possible_falcon_replicate_automation package is part of the npm ecosystem, designed to facilitate automation tasks. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the possible_falcon_replicate_automation package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The package continuously republishes variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages. The malicious code can compromise the integrity of the npm ecosystem and affect developers' projects relying on this package.

How To Fix

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

npm uninstall possible_falcon_replicate_automation

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 possible_falcon_replicate_automation package until a secure version is released. You can also monitor your project for any dependencies that may indirectly rely on this package and remove them as necessary.

Conclusion

The possible_falcon_replicate_automation package has been identified as a vector for malicious code that compromises the npm ecosystem. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for possible_falcon_replicate_automation →

Share this vulnerability

FAQ

It is an npm package designed for automation tasks but has been compromised with malicious code.

The malicious code modifies your package.json, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately using 'npm uninstall possible_falcon_replicate_automation'.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall possible_falcon_replicate_automation

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