Which versions of hyper-request are malicious?

The following PyPI versions of hyper-request are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hyper-request if I installed it?

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

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

Yes — hyper-request is associated with the 2025-04-hyper-request 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 hyper-request 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 hyper-request (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyper-request across your stack and pipelines.

Malicious package

hyper-requestPyPI

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

MAL-2025-191763

Immediate action

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

pip uninstall hyper-request

What this malware does

The only functionality is to exfiltrated Roblox cookies. However, the current version does not contain the webhook url yet (see reqhandler.py)

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

Campaign: 2025-04-hyper-request

Reasons (based on the campaign):

exfiltration-browser-data

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e1cda738d6b1421d42ca48e9c401dd4f6ab89d2613c80ef21d0b449007877331

d6431cc277fd1d8f82ec5160b5943d5ee9ec08ca1a5c5ff9b1b45d67c233b1d2

3dd9f4ae794c3f1023df0c80b66dd75d20179277f7588fd87799265bfadee28e

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

Campaign

2025-04-hyper-request

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks hyper-request-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