Which versions of request-httpx-4 are malicious?

The following PyPI versions of request-httpx-4 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate request-httpx-4 if I installed it?

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

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

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

Malicious package

request-httpx-4PyPI

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

MAL-2026-1001

Immediate action

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

pip uninstall request-httpx-4

What this malware does

The package contains a Telegram bot running allowing for remote access. This functionality is disclosed in the readme, but the package name clearly indicates it's either a dependency confusion attempt or it's intended to be hidden from the user in the installed environment.

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

Campaign: 2026-02-request-httpx-4

Reasons (based on the campaign):

dependency-confusion
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
files-exfiltration

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b0c661d240f626319e5ff1e52562ca1d4a8a6c741126a91e4d46a9ed639cfc0d

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

Campaign

2026-02-request-httpx-4

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks request-httpx-4-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