Which versions of rjan3 are malicious?

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

How do I remediate rjan3 if I installed it?

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

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

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

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

Malicious package

rjan3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8528

Immediate action

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

gem uninstall rjan3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

65feac8285dc359001d20725e5cb5a71358af097c2d21f1773b63c54c979de24

96942fecf18b53f00c1cffbf97860576bdcb86d57bd54b844dec2213e324e9e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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