Which versions of python-requirements-inspector are malicious?

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

How do I remediate python-requirements-inspector if I installed it?

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

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

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

Malicious package

python-requirements-inspectorPyPI

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

MAL-2025-49320

Immediate action

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

pip uninstall python-requirements-inspector

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 'python-requirements-inspector' @ 999.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

999.0.0999.0.1

Indicators of compromise (SHA-256)

120f942e828e97f95448695e19e77003953dfc19d2010c361a02e8d62d2efe7e

e6808df80e0d2778ba46ec1c965dba0300ef7864ef4d1b3dbf9b6877a9f18028

cc2b5ec947519cc5f4d537180821059db4c8d83050c93d36239acf1a8c71af4e

7f0753619f8f552a04b9dcc17080484d476562561f65ad57ac0d307939555510

8f26b5cd7ab7cb6a847edc1afec2dc496ac0f0bd3f592f2a98391365298c4fc6

9f56a5f4c4b84f7fe25aaedbec24051ce3632f14a63d5addd0d0f1cfd384f498

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-requirements-inspector (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-requirements-inspector across your stack and pipelines.
If you installed it — respond
python-requirements-inspector 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-requirements-inspector 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-requirements-inspector 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-requirements-inspector on PyPI has been identified as a malicious package (versions 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-05629GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks python-requirements-inspector-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