Which versions of beunlder are malicious?

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

How do I remediate beunlder if I installed it?

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

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

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

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

Malicious package

beunlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in beunlder (RubyGems)

MAL-2026-16586

Immediate action

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

gem uninstall beunlder

Malicious versions

2 flagged

1.0.01.0.46613

Indicators of compromise (SHA-256)

80f0d79bb0747328d8d392dd42e820d3d1055cdeacece5db9fc56ec8ed7bc716

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07244

Credits

ReversingLabs · finder

Detect & block this

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