Which versions of lowui are malicious?

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

How do I remediate lowui if I installed it?

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

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

Yes — lowui is associated with the RLMA-2024-11080, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00482 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 lowui 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 lowui (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lowui across your stack and pipelines.

Malicious package

lowuiPyPI

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

MAL-2024-11626

Immediate action

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

pip uninstall lowui

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c8c574a4ad6a557d05456ac7bfda28f9488ec7a458c83c0fc014536f0b872ca7

e1de75a31c2248e38fee03f867f8360ae7d0401b954f6134f880aa9519b975a4

c4ff92d988d3a1a5ad5fcec02556f08824926948c8d12fc1dba370a99b5e4b70

55a0c592b043c4f933680dca526489b6b8779d0f27d9f609e87de885f9d1ce8a

4c1b608939532e3d6ed6f97eced78c1f3382bea20073967f80b731c28bfbf028

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 lowui (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lowui across your stack and pipelines.
If you installed it — respond
lowui 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 lowui 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 lowui 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. lowui 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-110802024-08-embeds-RealtekHDAudioManagerRLUA-2026-00482

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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