Malicious Code Injection in usual_fly_requirement Package

usual_fly_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97213: Malicious code in usual_fly_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 usual_fly_requirement package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is suspected to be involved in a token reward campaign that aims to manipulate developer reputation scores. It is designed to automatically generate and publish derivative packages, which can lead to a polluted npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the usual_fly_requirement package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, which can lead to a significant increase in the number of malicious packages in the npm registry. This poses a risk to developers who may unknowingly install these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall usual_fly_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 usual_fly_requirement package from your project by executing the command: 'npm uninstall usual_fly_requirement'. This will help mitigate the risk until a patched version is available.

Conclusion

The usual_fly_requirement package contains malicious code that poses a significant risk to developers using it. It is essential to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your projects by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for usual_fly_requirement →

Share this vulnerability

FAQ

The usual_fly_requirement package is an npm package that is part of a token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the proliferation of unwanted packages in the npm registry.

If you have installed the usual_fly_requirement package, it is crucial to uninstall it immediately and check for any updates or patches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground.

To prevent future vulnerabilities, regularly update your packages, monitor your dependencies, and utilize tools like Vulert for real-time alerts on open-source vulnerabilities.

How To Fix

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

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