Which versions of codeui are malicious?

The following PyPI versions of codeui are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate codeui if I installed it?

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

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

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

Search your lockfiles and build artifacts for codeui (version 0.0.1).

Malicious package

codeuiPyPI

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

Malicious code in codeui (PyPI)

MAL-2024-4903

Immediate action

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

pip uninstall codeui

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9e7aa87ed4b8e1d90a32669c080ea4d1b3b160983aa9ae6af4f3913f1bfe9cc2

3c2c7a77d60055e8623f8e2818604c95b294480b0934a979824606f715ba0700

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for codeui (version 0.0.1).
If you installed it — respond
Remove codeui 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 codeui 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. codeui on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03683RLUA-2024-07974

Credits

ReversingLabs · finder

Detect & block this

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