Which versions of bundper are malicious?

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

How do I remediate bundper if I installed it?

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

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

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

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

Malicious package

bundperRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundper (RubyGems)

MAL-2026-17014

Immediate action

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

gem uninstall bundper

Malicious versions

2 flagged

1.0.01.0.6071

Indicators of compromise (SHA-256)

8e8b5a073e3fc7e84d6fa5923ccdc3372ba80f3015ded6c9eef50af608ecb5ba

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07700

Credits

ReversingLabs · finder

Detect & block this

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