Which versions of oaijgitwelcpe are malicious?

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

How do I remediate oaijgitwelcpe if I installed it?

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

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

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

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

Malicious package

oaijgitwelcpeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8254

Immediate action

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

gem uninstall oaijgitwelcpe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7991f8efc1ae199a6b3941a78c1623017d5337bf9bc8fb04447b2cb5ac34d6ed

11e5b4a79df31ad5bf76d3c09093bce9b69c1daa937e28d7d1c5c17055bed65c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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