Which versions of bunlser are malicious?

The following RubyGems versions of bunlser are flagged malicious: 1.0.90438. Treat any of these as compromised.

How do I remediate bunlser if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlser (version 1.0.90438).

Malicious package

bunlserRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunlser is a confirmed malicious RubyGems package (MAL-2026-17099) that executes malicious code on install (malicious version 1.0.90438). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunlser (RubyGems)

MAL-2026-17099

Immediate action

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

gem uninstall bunlser

Malicious versions

1 flagged

1.0.90438

Indicators of compromise (SHA-256)

ca626dce9f41434ae4c3a6c6160f2fbb56642fa3ea7ac8330842370c3d680123

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07785

Credits

ReversingLabs · finder

Detect & block this

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