Which versions of testexfragabc are malicious?

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

How do I remediate testexfragabc if I installed it?

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

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

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

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

Malicious package

testexfragabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8970

Immediate action

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

gem uninstall testexfragabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3376dbeb8bd077464b98850aabdd74b3538fbafbc601d83db85e96ecb1e24bb5

9b0a26c88e5e6fc565e0cd2b00ed45bbf91cbbecf61de590885347cf417688ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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