Which versions of batch-it are malicious?

The following RubyGems versions of batch-it are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate batch-it if I installed it?

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

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

Yes — batch-it is associated with the RLMA-2024-05563, RLUA-2024-10082 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 batch-it across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for batch-it (version 0.1.0).

Malicious package

batch-itRubyGems

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

Malicious code in batch-it (RubyGems)

MAL-2024-6757

Immediate action

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

gem uninstall batch-it

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

f94bda6ca2fa362300c29d7a0277cdef72cc431fa6dda7b764befff2a858a0ca

9f2515b14d3ebfd7f1f8f7de11fed88c61c0d2d884faecb1d027f3fc40fb24c8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05563RLUA-2024-10082

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks batch-it-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