Which versions of sgjcvwjwwo are malicious?

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

How do I remediate sgjcvwjwwo if I installed it?

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

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

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

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

Malicious package

sgjcvwjwwoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8611

Immediate action

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

gem uninstall sgjcvwjwwo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d6da421c9b874904cb3ed6e0353c979fa15e30c7ddae689abfc69e2d8c39a8b

9480d72f5133fcee2f51c6575f0e79cade77f5260032d1ab2ca36fb2d2e9f381

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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