Which versions of hyperreq are malicious?

The following PyPI versions of hyperreq are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate hyperreq if I installed it?

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

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

Yes — hyperreq is associated with the RLMA-2024-08393, 2024-09-hyperreq, RLUA-2026-00415 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 hyperreq 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 hyperreq (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyperreq across your stack and pipelines.

Malicious package

hyperreqPyPI

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

MAL-2024-10035

Immediate action

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

pip uninstall hyperreq

What this malware does

Importing the module starts an Infostealer

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

Campaign: 2024-09-hyperreq

Reasons (based on the campaign):

infostealer
obfuscation
files-exfiltration

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

37e2709d12922117af22c592107a8d63ff8fae91a1aea57c033e745402d7929d

e78641dd24ea1d314c2c0bbeaf454ef361ddc8d6a0368b0c5d41a5941f2ba3bc

a4662a05cce5bc61521e977b78c1abdb16ecaed027888309aa86ebf22166222b

7633082b53550eb0204482c5de65342c05321fa82a6bfe35d349e94c74dcffe9

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

Campaign

RLMA-2024-083932024-09-hyperreqRLUA-2026-00415

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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