Which versions of testgemoux174130 are malicious?

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

How do I remediate testgemoux174130 if I installed it?

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

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

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

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

Malicious package

testgemoux174130RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8978

Immediate action

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

gem uninstall testgemoux174130

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b0cf349cfc341c2b66640cae451c864e183c8d83c96f1adb5f06afe8a1274ded

f0bfc4300b4dbec9dddbc6b93e8e8871bcbf752b78ec886fc9867b200e3300d4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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