Which versions of python-rootpath are malicious?

The following PyPI versions of python-rootpath are flagged malicious: 0.1.1, 0.1.2, 0.1.3, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9. Treat any of these as compromised.

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

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

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

Yes — python-rootpath is associated with the 2025-11-python-rootpath, RLMA-2025-06584, RLUA-2026-00667 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 python-rootpath 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 python-rootpath (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-rootpath across your stack and pipelines.

Malicious package

python-rootpathPyPI

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

MAL-2025-191841

Immediate action

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

pip uninstall python-rootpath

What this malware does

Hidden code downloads, saves and import a remote script. The package itself is a clone of a legitimate "rootpath". At the time of analysis, the remote script did not do any harmful action

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

Campaign: 2025-11-python-rootpath

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
clones-real-package

Malicious versions

8 flagged

0.1.10.1.20.1.30.1.50.1.60.1.70.1.80.1.9

Indicators of compromise (SHA-256)

894d7db316da52e9be82cf9fc3b3c09a36a51beca269246cbc823de15005ee2e

bb867560d676e7b79ce110b230906a9630feb223cbcb6072bff5a2636c60a3c7

63d4c44546eaa9b33dc5fe1745f42e2966888ec5bb73df4369f8cdd982501fe2

e4dd471edee03aeb7579dbbbdbefa7594da826040e16473e4a99bf889788e832

f7e11676db9086d1238c4a81f42abebf09a400f09290aa05e3978f05b12872e3

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

Campaign

2025-11-python-rootpathRLMA-2025-06584RLUA-2026-00667

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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