Which versions of vacuole are malicious?

The following RubyGems versions of vacuole are flagged malicious: 22.55.2. Treat any of these as compromised.

How do I remediate vacuole if I installed it?

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

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

Yes — vacuole is associated with the RLMA-2024-05847, RLUA-2024-10368, RLUA-2026-09675 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 vacuole across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vacuole (version 22.55.2).

Malicious package

vacuoleRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

vacuole is a confirmed malicious RubyGems package (MAL-2024-7043) that executes malicious code on install (malicious version 22.55.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vacuole (RubyGems)

MAL-2024-7043

Immediate action

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

gem uninstall vacuole

Malicious versions

1 flagged

22.55.2

Indicators of compromise (SHA-256)

67dcc2b62611e36661db0861ef97f64cc10410ed510f99db4fbb619f8c20bbe2

9f9cfe89e087ce464d0a13c27d3ecbf9de266974ce0f27509177060154f78134

fe9b35affa8b3041d5ac23f0f387be288d7bf03c57bf6082e7af7b3ed42fd625

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05847RLUA-2024-10368RLUA-2026-09675

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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