Which versions of ruamel-poc are malicious?

The following PyPI versions of ruamel-poc are flagged malicious: 0.17.16, 1.17.16. Treat any of these as compromised.

How do I remediate ruamel-poc if I installed it?

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

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

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

Malicious package

ruamel-pocPyPI

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

MAL-2025-6010

Immediate action

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

pip uninstall ruamel-poc

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 'ruamel-poc' @ 0.17.16 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

0.17.161.17.16

Indicators of compromise (SHA-256)

8535b01286f7d33300d915d21bc5749c799fbac77f8bc63a9592c9e46afc1b3d

cebb357392e162b1d4864a43cb98290e8e053c3c629bccf4e5956d4985b39275

2035a1838e6e7355b22342eb1d9f34f68c2eead65a852b15806b2021478f4d83

1381375ccfff8dc10b3416284ac4a9a91c69bb2d5e7b652a2df24a64f4c5d512

99a4d31003b7e366ec2c24913976cb4622c234e345e7a7c32a1a5ee48ec0e3cc

36caea90ea40b08a55e0b66b70c46956b9f8e6981ffed3b19ece6e6a7ba776b2

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks ruamel-poc-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