Which versions of oaijanla are malicious?

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

How do I remediate oaijanla if I installed it?

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

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

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

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

Malicious package

oaijanlaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8240

Immediate action

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

gem uninstall oaijanla

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8c138aa85a675e9504d09e58f2cc64ee8bb3ff2fb70563f4a0be3d518afe652a

639f8e0ffc1e44620154b9eb3036e8d847a943b8fc20755cdda9c238a7429e95

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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