Which versions of runway-python are malicious?

The following PyPI versions of runway-python are flagged malicious: 0.0.1, 999.0.0, 999.0.1. Treat any of these as compromised.

How do I remediate runway-python if I installed it?

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

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

Yes — runway-python is associated with the RLMA-2025-03678, RLUA-2025-05637, GENERIC-standard-pypi-install-pentest, RLUA-2026-00739 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 runway-python 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 runway-python (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging runway-python across your stack and pipelines.

Malicious package

runway-pythonPyPI

Malicious code in runway-python (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6579

Immediate action

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

pip uninstall runway-python

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'runway-python' @ 999.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged

0.0.1999.0.0999.0.1

Indicators of compromise (SHA-256)

941e933ab612d3bebffcf1c501fc27de5ded3121e8516cbdbe543a514823be2e

565db55064e7acb20e69d3ebb2ac7ae1fb4ad9c38401d9f9dd49a58792bedc5c

99fe0a6c8206948cff292948efcdfea03d31a23852a9031662c32773cf3419ce

dc36e55f799568c3352b59426a04886afaeadd7a554e3f7c83f32e93ed3621f3

bd362f651f8b63f7dce107027deca96802c6e6b362c8552fe35a4ebc57966d97

ab69fc94c1b9d37312b22a4c970856a3b27f84b4f7e957ff2771a2244a527264

df207ff32989791c054aa64e43f8438c2fc6020322ee5e9ffe6b4d5502157803

a74543e4f56de9066221e355bd7c3613a6c356d2351264596681f4b8830af25c

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

Campaign

RLMA-2025-03678RLUA-2025-05637GENERIC-standard-pypi-install-pentestRLUA-2026-00739

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks runway-python-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