Which versions of rjan5 are malicious?

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

How do I remediate rjan5 if I installed it?

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

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

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

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

Malicious package

rjan5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

rjan5 is a confirmed malicious RubyGems package (MAL-2026-8530) 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 rjan5 (RubyGems)

MAL-2026-8530

Immediate action

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

gem uninstall rjan5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

371d121c5f79d8b1e5b6cb5e64551b7c4d064b5ab1f477bacbec19e23ea67995

bd5c06117147497ab6c78e6e2fa896b3e554be79b52b8edbc165c2bb62d4c766

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rjan5 (version 0.0.1).
If you installed it — respond
Remove rjan5 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 rjan5 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. rjan5 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-03181RLUA-2026-09068

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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