Which versions of hmac2 are malicious?

The following PyPI versions of hmac2 are flagged malicious: 0.0.1, 0.0.2, 0.0.2rc0. Treat any of these as compromised.

How do I remediate hmac2 if I installed it?

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

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

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

Malicious package

hmac2PyPI

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

MAL-2024-12287

Immediate action

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

pip uninstall hmac2

What this malware does

The package contains obfuscated code that exfiltrate basic data, and then executes commands delivered from remote server

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

Campaign: 2024-10-hmac2

Reasons (based on the campaign):

obfuscation
dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-generic

Malicious versions

3 flagged

0.0.10.0.20.0.2rc0

Indicators of compromise (SHA-256)

aa701936e511c8660bdb35501d4992b32a9cf69b60b6a29d0469f6e3eaab6741

055915f62eab8a5fe37b7501a3ed565a2aba267bdd69e82acaa13525bacf41a1

f4c8ca7684a9f624376e65f4fb0ddfeb5900aafb96a722e1e5a8d30853fef470

e085b192f68f8e7a2d3649619f8bcb85a26f4e95d269808570bc81d3523a0839

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

Campaign

2024-10-hmac2

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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