Which versions of hubtik are malicious?

The following PyPI versions of hubtik are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate hubtik if I installed it?

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

If hubtik was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hubtik part of a known attack campaign?

Yes — hubtik is associated with the RLMA-2024-04030, RLUA-2024-08389 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 hubtik across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hubtik (version 1.0).

Malicious package

hubtikPyPI

hubtik is a confirmed malicious PyPI package (MAL-2024-5248) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hubtik (PyPI)

MAL-2024-5248

Immediate action

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

pip uninstall hubtik

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

271ac9b81c07a67ed557de016e91a28cd9cd9ae00cf9311d7702078da4f72544

b27926bff7a91b226442dbe8a41a6fc478c658d2779156969af03780bdccf4a5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hubtik (version 1.0).
If you installed it — respond
Remove hubtik 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 hubtik was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hubtik on PyPI has been identified as a malicious package (version 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04030RLUA-2024-08389

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database