Which versions of flycord are malicious?

The following npm versions of flycord are flagged malicious: 1.0.5, 1.0.6, 1.0.9, 1.1.0, 1.2.0, 1.2.4, 1.3.0, 1.3.1. Treat any of these as compromised.

How do I remediate flycord if I installed it?

Remove flycord from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed flycord — how do I know if it already compromised me?

If flycord was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is flycord part of a known attack campaign?

Yes — flycord is associated with the GHSA-cmr9-xfh6-fffv, RLMA-2026-01763 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find flycord across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flycord (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flycord across your stack and pipelines.

Malicious package

flycordnpm

Malicious code in flycord (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1198

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall flycord

What this malware does

The package flycord was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

8 flagged

1.0.51.0.61.0.91.1.01.2.01.2.41.3.01.3.1

Indicators of compromise (SHA-256)

2a8f9b1be8c669768e145dc79e2d5345b794d5b06f8e1b87a1371efce3339395

f477b30e27717915d1f5a29429d03c3ca68513e4c2b8faef87404ee2dd399324

c6c91dc461fa5af500ed51d31cd35a450fd4975466a48a212c8a51d2af73c4bc

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flycord (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flycord across your stack and pipelines.
If you installed it — respond
Remove flycord from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If flycord was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks flycord before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. flycord on npm has been identified as a malicious package (versions 1.0.5, 1.0.6, 1.0.9, 1.1.0, 1.2.0, 1.2.4, 1.3.0, 1.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cmr9-xfh6-fffvRLMA-2026-01763

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks flycord-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring