Which versions of testslnews795 are malicious?

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

How do I remediate testslnews795 if I installed it?

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

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

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

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

Malicious package

testslnews795RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8990

Immediate action

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

gem uninstall testslnews795

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

499ea54001cf2089ca2594910dcb02d6858de2430421e3519f65e160a187e0da

4d3a45fafa1f4e77e1e15b8b286598923257187f7a1ada23d8dc976d52d33a6e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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