Critical Malicious Code Vulnerability in flycord Package

flycord Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1198: Malicious code in flycord (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The flycord package is a Node.js library designed for creating Discord bots with enhanced functionalities. It allows developers to easily interact with the Discord API, providing features such as message handling, user interactions, and event management. However, the package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the flycord package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, making it a significant threat to users and their systems. The ramifications include potential data breaches, loss of control over systems, and the necessity for immediate security measures.

How To Fix

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

npm uninstall flycord

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

Currently, there are no effective workarounds to mitigate the risks associated with the flycord package. The only recommended action is to uninstall the package and secure your system.

Conclusion

The flycord package has been compromised, leading to a critical vulnerability that can fully compromise any system using it. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring of dependencies is essential to maintain security.

See every vulnerability recorded for flycord →

Share this vulnerability

FAQ

You should immediately uninstall the flycord package and rotate any sensitive information stored on your system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Keeping flycord installed poses significant risks, including unauthorized access to your system and potential data breaches.

The best recovery method is to uninstall the package and rotate all sensitive information. There is no patch available for this vulnerability.

While many npm packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for flycord.

How To Fix

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

npm uninstall flycord

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