Which versions of flycord are malicious?

The following PyPI versions of flycord are flagged malicious: 1.2.4. Treat any of these as compromised.

How do I remediate flycord if I installed it?

flycord is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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 2026-02-flycord 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 (version 1.2.4). 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

flycordPyPI

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

MAL-2026-1049

Immediate action

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

pip uninstall flycord

What this malware does

When the user uses the provided library, this package silently reports basic information and the result of the user's action to a hardcoded, obfuscated URL. Given the lack of an opt-out possibility, collection of usernames, obfuscated target and not disclosing it anywhere, it cannot be classified as telemetry.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-flycord

Reasons (based on the campaign):

obfuscation
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
action-hidden-in-lib-usage

Malicious versions

1 flagged

1.2.4

Indicators of compromise (SHA-256)

b2071af47a4b327550f5614253b291b893e0741e6f2ebe3b4378a4794696d211

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flycord (version 1.2.4). 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
flycord is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
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 PyPI has been identified as a malicious package (version 1.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-flycord

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Malware detection Runtime egress monitoring