Which versions of hackmiami are malicious?

The following PyPI versions of hackmiami are flagged malicious: 69.69.69. Treat any of these as compromised.

How do I remediate hackmiami if I installed it?

Remove hackmiami from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hackmiami — how do I know if it already compromised me?

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

Yes — hackmiami is associated with the RLMA-2025-03014, GENERIC-simple-tests, RLUA-2026-00373 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 hackmiami 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 hackmiami (version 69.69.69). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hackmiami across your stack and pipelines.

Malicious package

hackmiamiPyPI

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

MAL-2025-5117

Immediate action

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

pip uninstall hackmiami

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

69.69.69

Indicators of compromise (SHA-256)

acbba710cd9ee7d276b681634cfd25e7f4ceb87beb7a5542580cdedbee3674ea

2983ccb4bd59cf96c4f115fd0a76b924202bc909b33518abff545d95a4cc22b4

e88ae480f8c860a5102015dac0a5388dc4967c19787b95e88825a4f0eccf8dfe

cea0655d17b52bb9c50cf39693010940143730d21ff501c348c3e65c81c8e8b2

e02cf7c37416a431beb49618817c65120caff2430e7ecb8b0a16a6be747dd2a4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hackmiami (version 69.69.69). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hackmiami across your stack and pipelines.
If you installed it — respond
Remove hackmiami from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hackmiami 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 hackmiami 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. hackmiami on PyPI has been identified as a malicious package (version 69.69.69 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03014GENERIC-simple-testsRLUA-2026-00373

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks hackmiami-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring