Which versions of rqeuets are malicious?

The following PyPI versions of rqeuets are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate rqeuets if I installed it?

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

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

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

Malicious package

rqeuetsPyPI

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

MAL-2025-4239

Immediate action

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

pip uninstall rqeuets

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.

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

bdb47593f6fec408c63906f8074c90708bf84bf3c6e8c6d44102fd5d18dceca0

f73239c63b24cdf05e2568c6d875180d185df636bf964fcb77e29d7184579f87

92b72b3d477812895ac9758fb085afd1bc8840f817d7bcc491b4b36c8215e79d

23fce2f66a9ce5b82c8a0810a94b252169666ad4e3a70acf8ac3a83ed00c2a27

1025406da4a495aac1aba5794a7144196219cffb37ad868a4f040c09a06a2762

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

Campaign

RLMA-2025-02596GENERIC-standard-pypi-install-pentestRLUA-2026-00730

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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