Which versions of bundlwr are malicious?

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

How do I remediate bundlwr if I installed it?

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

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

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

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

Malicious package

bundlwrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlwr (RubyGems)

MAL-2026-17006

Immediate action

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

gem uninstall bundlwr

Malicious versions

2 flagged

1.0.01.0.52738

Indicators of compromise (SHA-256)

610e99cc3a61bc6da513a831d45d96d98edf6d676707c99aa9bfe6e9632c7ad0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07692

Credits

ReversingLabs · finder

Detect & block this

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