Which versions of request-wizard are malicious?

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

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

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

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

Yes — request-wizard is associated with the RLMA-2025-02528, 2024-09-hyperreq, RLUA-2026-00703 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 request-wizard 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 request-wizard (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 request-wizard across your stack and pipelines.

Malicious package

request-wizardPyPI

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

MAL-2025-3464

Immediate action

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

pip uninstall request-wizard

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

1.0.0

Indicators of compromise (SHA-256)

78a8bfe99574c1c0cd13d39df7360979887210c8e793d1d31802a7a1d4b8dbf4

bab173c5d84587fc6b04613e7b5bcdc521b621acfb140dbbff7b46b1464db591

ff748393cb55e78c43fea879bbd55034152148246aa8d45359cfa8517845e17c

eba96dd07fb793af1aaaeedb33fde4ae0585a065db68edaa5a4c198fede8ed8d

1a0c4a1d5b6f5267f98d1779cc625e854c2def5861e52f7a92fa8f7043d485fe

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 request-wizard (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 request-wizard across your stack and pipelines.
If you installed it — respond
request-wizard 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 request-wizard 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 request-wizard 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. request-wizard 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

RLMA-2025-025282024-09-hyperreqRLUA-2026-00703

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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