Which versions of testssp-wukues are malicious?

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

How do I remediate testssp-wukues if I installed it?

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

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

Yes — testssp-wukues is associated with the RLMA-2026-03642, RLUA-2026-09566 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 testssp-wukues across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testssp-wukues (version 0.0.1).

Malicious package

testssp-wukuesRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

testssp-wukues is a confirmed malicious RubyGems package (MAL-2026-8991) 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 testssp-wukues (RubyGems)

MAL-2026-8991

Immediate action

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

gem uninstall testssp-wukues

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e8bd0a338bf0a2a71ba629d90f0c89901995b50eb30be0e38c215164dfe357ae

a7d927af4d76f108a8f2798957dfea4eedf5e8f50468d62a9dae2f7d498315db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks testssp-wukues-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