Which versions of rxlambjan are malicious?

The following RubyGems versions of rxlambjan are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate rxlambjan if I installed it?

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

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

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

Search your lockfiles and build artifacts for rxlambjan (version 0.0.1).

Malicious package

rxlambjanRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in rxlambjan (RubyGems)

MAL-2026-8546

Immediate action

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

gem uninstall rxlambjan

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

61d71097c25c0f43391c9fc47b8d4b11a2bc37c79a17b1db61fd684c1fe63a16

bf427e9fe65708b30c4ae23b0bd3c8d89859f8d903571eff2f05d7e9b7ed51ea

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03197RLUA-2026-09091

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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