Which versions of whssrftestabcxx are malicious?

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

How do I remediate whssrftestabcxx if I installed it?

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

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

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

Search your lockfiles and build artifacts for whssrftestabcxx (2 malicious versions).

Malicious package

whssrftestabcxxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

whssrftestabcxx is a confirmed malicious RubyGems package (MAL-2026-9361) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in whssrftestabcxx (RubyGems)

MAL-2026-9361

Immediate action

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

gem uninstall whssrftestabcxx

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

281d272941337d43416eb18fc329f1966f414eccd611f0cb362e877b86f17a84

a85f4f84b3c71a474952168413cc105792e1df6a0a4349b8a5da8052c97b9125

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for whssrftestabcxx (2 malicious versions).
If you installed it — respond
Remove whssrftestabcxx 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 whssrftestabcxx 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. whssrftestabcxx on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04012RLUA-2026-09942

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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