Which versions of http-request-toolkit are malicious?

The following PyPI versions of http-request-toolkit are flagged malicious: 2.28.3, 2.28.4, 2.28.5. Treat any of these as compromised.

How do I remediate http-request-toolkit if I installed it?

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

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

Yes — http-request-toolkit is associated with the 2026-02-requests-toolkit, RLMA-2026-00396 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 http-request-toolkit 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 http-request-toolkit (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging http-request-toolkit across your stack and pipelines.

Malicious package

http-request-toolkitPyPI

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

MAL-2026-912

Immediate action

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

pip uninstall http-request-toolkit

What this malware does

During import, package masquerade and starts an embedded executable. The executable has signs of infostealer activity

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

Campaign: 2026-02-requests-toolkit

Reasons (based on the campaign):

impersonation
infostealer
malware
The package contains code to detect if it is running in a sandbox environment.
keylogger

Malicious versions

3 flagged

2.28.32.28.42.28.5

Indicators of compromise (SHA-256)

13b29a753802db633ab987963543535999a246049761d4d29699b66edf207f13

8611f488d8714ccabd0499250be69556cbaffbf4b7e0bc18b179bde7fff3d722

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

Campaign

2026-02-requests-toolkitRLMA-2026-00396

References

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

O3 blocks http-request-toolkit-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