What does the hkmat 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 hkmat are malicious?

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

How do I remediate hkmat if I installed it?

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

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

Yes — hkmat 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 hkmat 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 hkmat (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 hkmat across your stack and pipelines.

Malicious package

hkmatPyPI

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

MAL-2025-191759

Immediate action

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

pip uninstall hkmat

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)

1297cb7ab5254f5324b2bf09802d5e20482d3e6d8bbc02ae514a97d8dd5883ad

c3c3063747c35c5ae091331ac2c35dbef66c945aca73b06ee32ef1f0ec088009

654aa9ece07b7c88baca510b7929527765db14eb99ef949546543ae64ba6c105

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