Which versions of ssrftestxyznever are malicious?

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

How do I remediate ssrftestxyznever if I installed it?

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

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

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

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

Malicious package

ssrftestxyzneverRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8896

Immediate action

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

gem uninstall ssrftestxyznever

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

8e3eb512a90a73bf61bc44913c6d046f670b4bd1b37f150162865d4cea661364

e81756f9fe15add1b85c9fc345434133b96d6fa709206a20366a0561c75af5f0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ssrftestxyznever (2 malicious versions).
If you installed it — respond
Remove ssrftestxyznever 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 ssrftestxyznever 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. ssrftestxyznever 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-03547RLUA-2026-09456

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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