Which versions of hazard are malicious?

The following PyPI versions of hazard are flagged malicious: 1. Treat any of these as compromised.

How do I remediate hazard if I installed it?

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

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

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

Search your lockfiles and build artifacts for hazard (version 1).

Malicious package

hazardPyPI

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

Malicious code in hazard (PyPI)

MAL-2024-5199

Immediate action

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

pip uninstall hazard

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

a1396a19a8c8147e3c1a6347aa1fad6bf7f84e4fe65aea3f54afef07344c0e4f

55d2377dbc4c5863ba272f42ea159a61c4217818cf8aa34584539e0831c4db55

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03981RLUA-2024-08341

References

Credits

ReversingLabs · finder

Detect & block this

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