Which versions of bundlsf are malicious?

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

How do I remediate bundlsf if I installed it?

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

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

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

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

Malicious package

bundlsfRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlsf (RubyGems)

MAL-2026-17001

Immediate action

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

gem uninstall bundlsf

Malicious versions

2 flagged

1.0.01.0.88915

Indicators of compromise (SHA-256)

8575ee9b71235c8496198b4ff9b2c59f51b30838647e5c2701a4194aebd1b2d3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07687

Credits

ReversingLabs · finder

Detect & block this

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