Which versions of uconst are malicious?

The following PyPI versions of uconst are flagged malicious: 1.0.0, 1.0.0rc1, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate uconst if I installed it?

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

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

Yes — uconst is associated with the RLMA-2024-09455, 2024-08-uconst-old, RLUA-2026-00869 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 uconst 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 uconst (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uconst across your stack and pipelines.

Malicious package

uconstPyPI

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

MAL-2024-10179

Immediate action

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

pip uninstall uconst

What this malware does

Package "uconst" is the package containing malicious code with multiple stage, exfiltrating basic info as well as browser data. It's put into others as dependency.

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

Campaign: 2024-08-uconst-old

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

4 flagged

1.0.01.0.0rc11.0.11.0.2

Indicators of compromise (SHA-256)

9175010462ad636ec5813f6478c062e03a63ccb0ee009c3bf01f1db999a40a4a

8ea8426ed09014407e1aa4060f5913904a0be81975c1b3a9521d8950ac5a303b

cc4ce4d1709ad506513007356fd414ca83c1aa848f9134e952c4b760194428c6

e606007896b8e5ae4cdd0a13e41487b68d5c2c822db34d35fb5d9679bd357f15

cd22a2c39c3c613666ec96db47b474c8450f88a91ed4a854b1895310734c5b53

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

Campaign

RLMA-2024-094552024-08-uconst-oldRLUA-2026-00869

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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