Which versions of haybales are malicious?

The following RubyGems versions of haybales are flagged malicious: 90002.0. Treat any of these as compromised.

How do I remediate haybales if I installed it?

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

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

Yes — haybales is associated with the RLMA-2025-06613, RLUA-2026-08180 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 haybales across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for haybales (version 90002.0).

Malicious package

haybalesRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

haybales is a confirmed malicious RubyGems package (MAL-2025-192906) that executes malicious code on install (malicious version 90002.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in haybales (RubyGems)

MAL-2025-192906

Immediate action

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

gem uninstall haybales

Malicious versions

1 flagged

90002.0

Indicators of compromise (SHA-256)

bd536daa96e6efeee28c0a1c67e9098816d6403075417841bf3496aa25f81cf5

911013a72bf77ed3ebc94e6f8c56adf742a1917d6cea017240038e0ea58ff797

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06613RLUA-2026-08180

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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