Which versions of code-beautifyer are malicious?

The following PyPI versions of code-beautifyer are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate code-beautifyer if I installed it?

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

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

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

Malicious package

code-beautifyerPyPI

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

MAL-2025-908

Immediate action

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

pip uninstall code-beautifyer

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d488b278169f3b04ac012af1a9132966dcbb6964685157a75807f3846075ea92

dd9419749065959c875a1a95a399e5517ed427b06ad8ef0558862872dd279399

1aa07cb2a8c34d8fc5a6728b0985541456937811451149748ae9acdef4892e7c

a87c448eb7a501cdce862c2783a5b19e2e9ea11f1792105a0953b388ef1360b2

683a7f860daf2471b442f9a7d4c885db7272af1db4b8f07574c6b23fcf75d168

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

Campaign

RLMA-2025-004462024-12-langer-updaterRLUA-2026-00200

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks code-beautifyer-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