Which versions of rjan2 are malicious?

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

How do I remediate rjan2 if I installed it?

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

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

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

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

Malicious package

rjan2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8527

Immediate action

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

gem uninstall rjan2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bbf8adaa58598cf0f44ecf33a4de80836e5575f0f69bf0e3859e416bb47291b4

66601163447254d86a215bb131f6d85d2e73b7a76f78c696b60fe70e4471f3e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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