Which versions of langer-updater are malicious?

The following PyPI versions of langer-updater are flagged malicious: 1.0.2, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate langer-updater if I installed it?

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

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

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

Malicious package

langer-updaterPyPI

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

MAL-2025-942

Immediate action

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

pip uninstall langer-updater

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

6 flagged

1.0.21.0.41.0.51.0.61.0.71.0.8

Indicators of compromise (SHA-256)

1108ee0779c828b294036aefa3c03de4ee1ee1cef5a5fbc2dd73fd6693b142b3

01890656caa2f6b8d2e17ddfc46836107703af4a2b5ad9406f3d8b8129db43d3

1d2e888da57bf1c53e73ed2092516a44aaf46e4876619d129b7e3e4966dfc71e

8f3f587200a6dcf8dbf257940771c47592b915fe47804bb431c8316b4d239659

e33616ad16b6559a64f0a945bf93f21ac1eed92f103d190018278b71f5397e92

913cf586f92492ecf7f7f960011b7ceff827b978b02d240bf35d159d6c7e7d55

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

Campaign

RLMA-2025-004822024-12-langer-updaterRLUA-2026-00462

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks langer-updater-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