What does the hekamhelp malware do?

Importing the module starts a telegram bot that connects to a chat and executes provided commands Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-talbat Reasons (based on the campaign): - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Which versions of hekamhelp are malicious?

The following PyPI versions of hekamhelp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hekamhelp if I installed it?

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

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

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

Malicious package

hekamhelpPyPI

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

MAL-2025-191750

Immediate action

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

pip uninstall hekamhelp

What this malware does

Importing the module starts a telegram bot that connects to a chat and executes provided commands

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

Campaign: 2025-07-talbat

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f42c94af8ec585c4e1aa7b7b56b159e6a9f69e876a8f757760a585226bfb46fe

ac329f6244d2faf82ef12a167d1b46de2a9043fb1c086b67a45458d75d227562

0b67e6c3295e1f387f6cd0d6f79be56a1a47448714c1055f9b60bfe189917604

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

Campaign

2025-07-talbat

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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