Which versions of lan-clean are malicious?

The following PyPI versions of lan-clean are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate lan-clean if I installed it?

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

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

Yes — lan-clean is associated with the RLMA-2025-00480, 2024-12-langer-updater, RLUA-2026-00461 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 lan-clean 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 lan-clean (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lan-clean across your stack and pipelines.

Malicious package

lan-cleanPyPI

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

MAL-2025-940

Immediate action

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

pip uninstall lan-clean

What this malware does

During installation, the package collects quite extensive information about the host and has no other purpose. To avoid detection, the real code is put in a ZIP archive and includes also some VM-detection techniques. The malicious code is activated via metaclass set for the "install" command class in setup.py

Over the time, techniques used in packages are slightly changing, including that some of marked packages don't have malicious part, but rather are used only for tests.

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

Campaign: 2024-12-langer-updater

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-env-variables
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

7a093bfe58bab9471a354252ac8cc3b4457cfd1120edfb7c09bd317758559992

fd178a2cdd22e49c36c695ea70c4aa140a6a890e7c7e585bde24b82050294574

b77907fa5398dac2959c2fa6cc7ab1c451a318803ca9efb40ea52487080609c3

52a773a568dee28c88213a6a1e76eee34fcaa5a9a7c74b71f161fab9eb3aee10

931e79a3565c6eccddd3c44ec9563796b8b5077afeb73d88fa8a3469a9382b9d

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

Campaign

RLMA-2025-004802024-12-langer-updaterRLUA-2026-00461

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks lan-clean-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