Which versions of requestpackat are malicious?

The following PyPI versions of requestpackat are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate requestpackat if I installed it?

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

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

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

Malicious package

requestpackatPyPI

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

MAL-2025-5127

Immediate action

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

pip uninstall requestpackat

What this malware does

Code download and runs an executable, which is widely recognized as malware. The system is also configured to run it on startup, and the file is saved in paths attempting to look as a system file.

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

Campaign: 2025-05-requestpackat

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
peristence-autorun

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

bd9fa31de2e6585f8ff120c4dc6ec856376f193db6aaafc59c77c2ebdaae7af3

8ec797580e984c82836fdf3d52adc8441744a46da5d0f602f189a96fba6a9c1f

b70e437edd04a30f48e384a4a07cdb1790dcb5e6a66ba800dc1703bf845a6b36

ee2729f4331f0e1f42f440b377e789ff4b1afcdc427986769e6fcdfad25167ce

f70b8dd5337e5eac2517248cbc9fe4266de761329e07af3c8597d85a98b42b41

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

Campaign

RLMA-2025-030242025-05-requestpackatRLUA-2026-00704

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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