Malicious Code Exploit in spatial_falcon-appteadev Package

spatial_falcon-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108974: Malicious code in spatial_falcon-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spatial_falcon-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious code. The vulnerability arises from its ability to generate and publish derivative packages with random names, which can lead to reputation inflation and pollution of the npm registry.

Vulnerability Detail

The vulnerability in the spatial_falcon-appteadev package is rooted in its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can severely impact the integrity of the npm registry. This behavior not only compromises the affected package but also poses a risk to developers relying on npm for secure package management. The malicious scripts are designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall spatial_falcon-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 spatial_falcon-appteadev package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall spatial_falcon-appteadev.

Conclusion

The spatial_falcon-appteadev package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects.

See every vulnerability recorded for spatial_falcon-appteadev →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and generates random package names, leading to npm registry pollution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

The risks include compromised package integrity, potential security breaches, and the pollution of the npm registry, affecting other developers.

Check the npm registry for any patched versions of the spatial_falcon-appteadev package and update accordingly.

As a temporary measure, uninstall the spatial_falcon-appteadev package from your project to mitigate risks.

How To Fix

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

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