Which versions of testgemfooabc are malicious?

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

How do I remediate testgemfooabc if I installed it?

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

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

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

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

Malicious package

testgemfooabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8976

Immediate action

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

gem uninstall testgemfooabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0a215175d012bd2277770f06e11b8b128dd92b8fc95676dbf0f7dc3d19e60734

7ff32b282213450d23180b698eebe5cf92852532c0a051d11df9e7e4bdf5cbfd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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