Which versions of oaijfossilgsvaqj are malicious?

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

How do I remediate oaijfossilgsvaqj if I installed it?

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

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

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

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

Malicious package

oaijfossilgsvaqjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8248

Immediate action

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

gem uninstall oaijfossilgsvaqj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

12cd67eaab775cc2b44385cedf02a1a343c365fc55e56064e1038e3055e7c7eb

50ed2bd79ba263bceb6964587c710eabd720c4f3740160c58d289bbaa82a17d4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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