Which versions of lyroxpy are malicious?

The following PyPI versions of lyroxpy are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate lyroxpy if I installed it?

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

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

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

Malicious package

lyroxpyPyPI

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

MAL-2026-841

Immediate action

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

pip uninstall lyroxpy

What this malware does

The package contains an embedded archive with an executable. When importing the module, the embedded archive is run as a module. Code inside extracts the executable and saves it to a temporary file. Further the code keeps an open file handler and removes the original file, effectively making the impression the file no longer exists. Using the file handler the executable (which is either a native Python module or was created from Python code) is run. Further behavior is not known.

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

Campaign: 2026-02-lyroxpy

Reasons (based on the campaign):

obfuscation
covering-tracks

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

a9016ac99840c4d68028c7b724382974154c9bf75b410da9c6b4a75ff6d20b1f

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

Campaign

2026-02-lyroxpy

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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