Which versions of testqwertyabcabc are malicious?

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

How do I remediate testqwertyabcabc if I installed it?

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

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

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

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

Malicious package

testqwertyabcabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8989

Immediate action

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

gem uninstall testqwertyabcabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fdb9f1b6233f2864c4e8dab2f453837086c947528843e9497da9d6cb3171b18d

60f7aed4cff2f345e07b8ae03b7219d2247203928b486f6399a2b3905fa2a67d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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