Which versions of designtestabc01 are malicious?

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

How do I remediate designtestabc01 if I installed it?

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

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

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

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

Malicious package

designtestabc01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7612

Immediate action

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

gem uninstall designtestabc01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9f06839bf3bd5b5490012914a95a168be5597579f2e4965c481b5a46dc5b853b

47d0e50acb87c1043bf54fbd03063afd4ca12c5a37aa13e5260a69820da5d52a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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