Which versions of uus are malicious?

The following PyPI versions of uus are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate uus if I installed it?

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

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

Yes — uus is associated with the RLMA-2024-11203, 2024-11-byted-dast, RLUA-2026-00882 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 uus 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 uus (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uus across your stack and pipelines.

Malicious package

uusPyPI

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

MAL-2024-11742

Immediate action

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

pip uninstall uus

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

Malicious versions

1 flagged

912.6

Indicators of compromise (SHA-256)

1c9e4664692b1fe138f00caa04fb4a73a606dcb1ad2b52eee21422d48bcb9893

6bcbe97d83493abf86dd220093be30425fe8383ccdf94df8c9715cd0b6212f58

30ca4330f972788b6c86dd1f758c674796e53ffc99cf686ac2ed551110ba3830

c744ad6a9002abb8edf8b0c1b049a872ebf2982144cf308b59e79ef8a030da77

93112c0f5d086494b8bb763da459a97e945002021f1124be238476bec139f7b6

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

Campaign

RLMA-2024-112032024-11-byted-dastRLUA-2026-00882

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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