Which versions of bsundlef are malicious?

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

How do I remediate bsundlef if I installed it?

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

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

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

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

Malicious package

bsundlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bsundlef (RubyGems)

MAL-2026-16761

Immediate action

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

gem uninstall bsundlef

Malicious versions

2 flagged

1.0.01.0.40107

Indicators of compromise (SHA-256)

33a86b37f9584c7924ed49fb992ac51c053d9431ef90bfcd37901e3c162d790a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07446

Credits

ReversingLabs · finder

Detect & block this

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