Which versions of testparamhg6 are malicious?

The following RubyGems versions of testparamhg6 are flagged malicious: 0.0.27779. Treat any of these as compromised.

How do I remediate testparamhg6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for testparamhg6 (version 0.0.27779).

Malicious package

testparamhg6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

testparamhg6 is a confirmed malicious RubyGems package (MAL-2026-8983) that executes malicious code on install (malicious version 0.0.27779). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testparamhg6 (RubyGems)

MAL-2026-8983

Immediate action

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

gem uninstall testparamhg6

Malicious versions

1 flagged

0.0.27779

Indicators of compromise (SHA-256)

05521cfe1a8b7059fa48725e4315408a852f1ff478907c9b6c218e15f74aee69

1b5e83318cf1eefd678d84a13c8ff7c5ae63f1af451a20a41d6a17157aa49ac8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03634RLUA-2026-09558

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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