Which versions of hexteamibm are malicious?

The following PyPI versions of hexteamibm are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate hexteamibm if I installed it?

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

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

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

Malicious package

hexteamibmPyPI

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

MAL-2024-12285

Immediate action

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

pip uninstall hexteamibm

What this malware does

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-07-hexmanibm

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

f065e98cc983e968f39ebdbf6d712dfcdb2b7b66e8ef1708a1be0005f20d3864

7e39a6455fe7cac6fa055a3c30ea55393ca098996f1497564f4aefb6f907805a

177fad5db442840c2d0df8e340733049be63a6b990cba8c87e40e7cd9d0b355e

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

Campaign

2024-07-hexmanibm

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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