Which versions of httpserver-cache are malicious?

The following PyPI versions of httpserver-cache are flagged malicious: 3.13.1, 3.14.0. Treat any of these as compromised.

How do I remediate httpserver-cache if I installed it?

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

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

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

Malicious package

httpserver-cachePyPI

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

MAL-2025-191632

Immediate action

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

pip uninstall httpserver-cache

What this malware does

Packages silently decrypt content hidden in a dependency and load them as Python extension modules.

In the first wave, those are copies of legitimate aiohttp and aiohappyeyeballs packages. In the second wave, malicious packages created good-looking forks of legitimate rich and pigments packages.

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

Campaign: 2025-10-asynhttp

Reasons (based on the campaign):

typosquatting
exfiltration-generic
obfuscation
clones-real-package
native-extension

Malicious versions

2 flagged

3.13.13.14.0

Indicators of compromise (SHA-256)

b844fd19cd54946f87975380d6567c6735c58e57248053c3c49c403d58617553

b6d14c1a0634b7c0ebef204b42090ed65d5b0246f29b8707d35794830096fdea

e7a215e207f060c3cd06c2ca78ad57787473b5a9509572b34c4e0fd873bc1a85

f48fad5068e7bfd86223ca6ef2fbf939ae684f2a4ae499f15f9cbe1e0cd9144d

cf6cc2d765cfb74609601f71d8c0fd9b7afe63c6821e1d840b08e3c1fb9f1f0d

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

Campaign

RLMA-2025-056012025-10-asynhttpRLUA-2026-00400

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks httpserver-cache-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