Which versions of upllib are malicious?

The following PyPI versions of upllib are flagged malicious: 1, 1.0. Treat any of these as compromised.

How do I remediate upllib if I installed it?

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

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

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

Malicious package

upllibPyPI

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

MAL-2024-11736

Immediate action

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

pip uninstall upllib

What this malware does

When importing the module and a specific file exists in the current directory, obfuscated code downloads and starts the next stage of obfuscated code (cstealer infostealer)

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

Campaign: 2024-10-pyutiltool

Reasons (based on the campaign):

infostealer
obfuscation
infostealer:cstealer

Malicious versions

2 flagged

11.0

Indicators of compromise (SHA-256)

3e2724ad7f14027e907a4cee699360a47bddea1e86c2bd183fe9e1c65298ef74

bb28e3795acba47121f078eb76292875a57d1a1a687f9e41d924c5dfaa000d9b

6207428c93f872f851e291726fc7a7384f9226b903c01a5a3f1545f82d66bf0b

250e442532abf631f411adc5b3ce5d10d2d1abdd6ac4538e54df3d08d9acdc81

b5fb81e066eacbca3ddd0f9e0df5d283b6bfc8bce9d92559bd284a32123bcb9a

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

Campaign

RLMA-2024-111972024-10-pyutiltoolRLUA-2026-00873

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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