Which versions of oaipwysipnjet are malicious?

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

How do I remediate oaipwysipnjet if I installed it?

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

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

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

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

Malicious package

oaipwysipnjetRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8331

Immediate action

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

gem uninstall oaipwysipnjet

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b22ab35284eb8aa947ccdba115a3540eb2efb7606adb7fcf83809c41958fb4fd

9fb7ed6600eef320a53a1aaefda2ce561714c5c1b0713ad140d79b3a8e82ee0a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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