Which versions of bundleof are malicious?

The following RubyGems versions of bundleof are flagged malicious: 1.0.0, 1.0.98184. Treat any of these as compromised.

How do I remediate bundleof if I installed it?

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

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

Yes — bundleof is associated with the RLMA-2026-07647 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 bundleof across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bundleof (2 malicious versions).

Malicious package

bundleofRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundleof is a confirmed malicious RubyGems package (MAL-2026-16961) that executes malicious code on install (malicious versions 1.0.0, 1.0.98184). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundleof (RubyGems)

MAL-2026-16961

Immediate action

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

gem uninstall bundleof

Malicious versions

2 flagged

1.0.01.0.98184

Indicators of compromise (SHA-256)

7937cf66b850eaec0b2602757f508590d66d6b3a54dc9fe058367b463ce46a65

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07647

Credits

ReversingLabs · finder

Detect & block this

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