Which versions of updateuuid4 are malicious?

The following PyPI versions of updateuuid4 are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate updateuuid4 if I installed it?

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

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

Yes — updateuuid4 is associated with the 2025-02-updateuuid4 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 updateuuid4 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 updateuuid4 (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging updateuuid4 across your stack and pipelines.

Malicious package

updateuuid4PyPI

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

MAL-2025-191917

Immediate action

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

pip uninstall updateuuid4

What this malware does

The package, with an innocent looking name, has as the only functionality reporting to a Telegram channel given username and password. The functionality is in the "HeadersUpdate" class, that also looks like attempting to look innocent. The code does nothing more than reporting given credentials through a bot using the name "hitlercute_bot".

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

Campaign: 2025-02-updateuuid4

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

f47e11e9651002d011f792dcc8f929a7a81f917ae289b7e275bd11c1f494cf8c

2c45f904631a26aae94cafeeac5ea0f7efe0fc5d4f46dea48da17dcb766111d5

0349938b8d343ef81cf67c14c439d06f44aaf2d94f0e86ee4781fd3fbae4e36f

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

Campaign

2025-02-updateuuid4

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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