Which versions of lyroxcoder are malicious?

The following PyPI versions of lyroxcoder are flagged malicious: 1.0.0, 1.0.1, 2.0.1, 2.1.1, 2.1.3, 2.2.3. Treat any of these as compromised.

How do I remediate lyroxcoder if I installed it?

lyroxcoder 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 lyroxcoder — how do I know if it already compromised me?

If lyroxcoder 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 lyroxcoder part of a known attack campaign?

Yes — lyroxcoder is associated with the 2026-04-Lyrox 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 lyroxcoder 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 lyroxcoder (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lyroxcoder across your stack and pipelines.

Malicious package

lyroxcoderPyPI

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

MAL-2026-3015

Immediate action

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

pip uninstall lyroxcoder

What this malware does

Heavy obfuscate code for extracting further obfuscate binaries and executing them using file less techniques. Some versions contain the executable embedded, other require providing them externally.

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

Campaign: 2026-04-Lyrox

Reasons (based on the campaign):

obfuscation

Malicious versions

6 flagged

1.0.01.0.12.0.12.1.12.1.32.2.3

Indicators of compromise (SHA-256)

0aa87cfde7d0b832cd24067a43e94d812a4f5ce64541e219fb6aa6b7388939ab

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 lyroxcoder (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lyroxcoder across your stack and pipelines.
If you installed it — respond
lyroxcoder 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 lyroxcoder 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 lyroxcoder 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. lyroxcoder on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 2.0.1, 2.1.1, 2.1.3, 2.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-Lyrox

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks lyroxcoder-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