Which versions of hase are malicious?

The following PyPI versions of hase are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate hase if I installed it?

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

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

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

Search your lockfiles and build artifacts for hase (version 0.0.1).

Malicious package

hasePyPI

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

Malicious code in hase (PyPI)

MAL-2024-5196

Immediate action

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

pip uninstall hase

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ae43e41ea6dc44ab1860e5bb1b4e446b6aa126228178c60309a228aea475c04e

8d2f1e893ea4b7d5998bf77ffb469496bbfdf9a969a8c757f857e1224f918963

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hase (version 0.0.1).
If you installed it — respond
Remove hase 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 hase 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. hase on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03978RLUA-2024-08338

Credits

ReversingLabs · finder

Detect & block this

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