Which versions of bsunlder are malicious?

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

How do I remediate bsunlder if I installed it?

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

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

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

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

Malicious package

bsunlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bsunlder (RubyGems)

MAL-2026-16763

Immediate action

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

gem uninstall bsunlder

Malicious versions

2 flagged

1.0.01.0.12818

Indicators of compromise (SHA-256)

1065ae062ceeee25eb6b677a85cee4f573f3749add8fd7398040cb095fc083f5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07448

Credits

ReversingLabs · finder

Detect & block this

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