Which versions of rjan4 are malicious?

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

How do I remediate rjan4 if I installed it?

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

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

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

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

Malicious package

rjan4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8529

Immediate action

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

gem uninstall rjan4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

324202e15ecc9a0754160849a92393f35a140ab097828c6f4cc7258ac9a86188

05f1985633e3a5213a163c653f56d6ab62f6084330f57b1f0c9db6ed9ebe35fb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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