Which versions of oaitfossilxxipsj are malicious?

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

How do I remediate oaitfossilxxipsj if I installed it?

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

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

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

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

Malicious package

oaitfossilxxipsjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8342

Immediate action

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

gem uninstall oaitfossilxxipsj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3bcb2cdece1b1ddb86b38a0fb1f91bc0d9b60e532ed2c36bef12c82c4f49a439

6b046aa1ad0610df70937a1795fdcc2e0f38c352b2c5e2c380a9a45679324bcf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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