What does the libproxy malware do?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2023-11-update-information-endpoint Reasons (based on the campaign): - obfuscation - The package overrides the install command in setup.py to execute malicious code during installation. - typosquatting

Which versions of libproxy are malicious?

The following PyPI versions of libproxy are flagged malicious: 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate libproxy if I installed it?

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

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

Yes — libproxy is associated with the RLMA-2024-04105, RLUA-2024-08469, 2023-11-update-information-endpoint, RLUA-2025-06571, RLUA-2026-00469 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 libproxy 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 libproxy (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libproxy across your stack and pipelines.

Malicious package

libproxyPyPI

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

MAL-2024-5323

Immediate action

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

pip uninstall libproxy

What this malware does

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

Campaign: 2023-11-update-information-endpoint

Reasons (based on the campaign):

obfuscation
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

2 flagged

1.1.41.1.5

Indicators of compromise (SHA-256)

7a1de19c0b6f786a6b9c843b0d335c5ae50d88fdff834ead6ebebdf4c436e078

74f8d064b862b148e663a87a8d14e4cafc68127945e5c68b1287deb4e9f0a599

adb17ae6ab2259030fc73e0f78a7c7b05033afcedf19a1cdb822f17e12091cef

cd7d095572ec4dd86648a86d8a9ee88e4c5b11e02bc519a951d3c41539d6e6c0

d34fdee2a9c3f8662a837ad1e95e5bc279775b59910ed98c950b8ab756d204ec

d06059887d6f955e4c402a51e2d3c94d5fb82832f7eb1ea63726db5bcff09e70

498f6f401f20b62ea6bb08d2a78c46bb08fc354a753a2fdbc63d935271cf4332

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

Campaign

RLMA-2024-04105RLUA-2024-084692023-11-update-information-endpointRLUA-2025-06571RLUA-2026-00469

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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