Which versions of lalaproxy are malicious?

The following PyPI versions of lalaproxy are flagged malicious: 1. Treat any of these as compromised.

How do I remediate lalaproxy if I installed it?

Remove lalaproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed lalaproxy — how do I know if it already compromised me?

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

Yes — lalaproxy is associated with the RLMA-2024-04086, RLUA-2024-08450 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 lalaproxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lalaproxy (version 1).

Malicious package

lalaproxyPyPI

lalaproxy is a confirmed malicious PyPI package (MAL-2024-5304) that executes malicious code on install (malicious version 1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lalaproxy (PyPI)

MAL-2024-5304

Immediate action

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

pip uninstall lalaproxy

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

38d7fa1f8cc02b03d8ed2c5b5d8948e3382aa4b5eced5f86ed4598eec204d90c

7828640bf58aca9fd032e4906e5a2d6b30148c5ef16e4231a0d6759a74bf2128

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lalaproxy (version 1).
If you installed it — respond
Remove lalaproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If lalaproxy 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. lalaproxy on PyPI has been identified as a malicious package (version 1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04086RLUA-2024-08450

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks lalaproxy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database