Which versions of testlamb987 are malicious?

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

How do I remediate testlamb987 if I installed it?

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

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

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

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

Malicious package

testlamb987RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8980

Immediate action

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

gem uninstall testlamb987

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

00674288b6ffab950c6793de38ea9208adde2f8c77f8e52b43127d514b75ce39

a3b59b74c3dc845cb91ff338fcc3bc2c7754aa1159e64dd2f4618a1b3f448f61

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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