Which versions of h4xupdate are malicious?

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

How do I remediate h4xupdate if I installed it?

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

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

Yes — h4xupdate is associated with the 2026-05-h4xupdate 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 h4xupdate 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 h4xupdate (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 h4xupdate across your stack and pipelines.

Malicious package

h4xupdatePyPI

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

MAL-2026-5093

Immediate action

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

pip uninstall h4xupdate

What this malware does

Package contains a remote control tool taking orders from a hardcoded Telegram bot. The authorship impersonate legitimate company.

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

Campaign: 2026-05-h4xupdate

Reasons (based on the campaign):

rat
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
files-exfiltration
impersonation

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0de4da975d7b071824607be751a9ea0fb13e409eaef58d1cc0628263d5dea700

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 h4xupdate (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 h4xupdate across your stack and pipelines.
If you installed it — respond
h4xupdate 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 h4xupdate 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 h4xupdate 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. h4xupdate 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

2026-05-h4xupdate

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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