Which versions of helu are malicious?

The following PyPI versions of helu are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate helu if I installed it?

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

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

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

Malicious package

heluPyPI

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

MAL-2026-4357

Immediate action

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

pip uninstall helu

What this malware does

During import, the hidden code downloads and executes the second-stage code. After performing anti-analysis checks, it downloads a malicious executable and ensures its persistence.

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

Campaign: 2026-05-helu

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
The package contains code to detect if it is running in a sandbox environment.
Downloads and executes a remote executable.
malware
persistence
covering-tracks

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

15a97c1f0e23d838c86d69a3ceae306071a9b4b8c17162a1f563aefe489ffbe4

365db50e4566104dffd097ed4240ac1957071547975915509145670e5ad5fbea

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

Campaign

2026-05-helu

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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