Which versions of sgvtbcatnr are malicious?

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

How do I remediate sgvtbcatnr if I installed it?

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

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

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

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

Malicious package

sgvtbcatnrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8623

Immediate action

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

gem uninstall sgvtbcatnr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

17dbe74053342c129a11339106bf937659d8c6fa50ac18050a36f2432d3387a3

b03842ac44624435e6e9e136c5726e64cc87956d3553837a316d6b4fbdbfce62

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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