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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for request-httpx-4 (version 0.0.1).

Malicious package

request-httpx-4PyPI

Advisory published Feb 23, 2026Updated Feb 23, 2026

request-httpx-4 is a confirmed malicious PyPI package (MAL-2026-1001) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in request-httpx-4 (PyPI)

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
Search your lockfiles and build artifacts for request-httpx-4 (version 0.0.1).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Explore

All malware advisories How O3 detects malware Vulnerability database