Which versions of keytest943 are malicious?

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

How do I remediate keytest943 if I installed it?

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

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

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

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

Malicious package

keytest943RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7780

Immediate action

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

gem uninstall keytest943

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

22605be3690e500e574a1cf12806e47113b55b47a736ecbab16292a0ba4c889e

f7e72cc9913f6abe5abfdc32c07c5cae0636e0cc6a8e3fa68ff5dc5f4975cf5d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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