Which versions of rootjina18601 are malicious?

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

How do I remediate rootjina18601 if I installed it?

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

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

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

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

Malicious package

rootjina18601RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8535

Immediate action

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

gem uninstall rootjina18601

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4e45a9c45bf520886fa941abfbc38a1638f77485e98b1ab1b8811c535c647ad0

e3015afdff695b259b9a2a63ae9d565a6b26bbeb8d21d7eaa71800c739be7d98

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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