Malicious Code Injection in random_fly-appteadev: A Threat to npm Packages

random_fly-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107707: Malicious code in random_fly-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 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

random_fly-appteadev is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary function of this package is to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in random_fly-appteadev originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, including the installation of untrusted packages.

How To Fix

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

npm uninstall random_fly-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 avoid using the random_fly-appteadev package and replace it with a reputable alternative that serves the same purpose without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The random_fly-appteadev package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and ensure their applications are secure by using trusted alternatives and monitoring their dependencies.

See every vulnerability recorded for random_fly-appteadev →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with untrusted packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed random_fly-appteadev, you should uninstall it immediately using 'npm uninstall random_fly-appteadev' and review your dependencies for any other potentially harmful packages.

Yes, there are many reputable alternatives available on npm. Always check the package's documentation and community feedback before choosing an alternative.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

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