Which versions of sgpakpubiz are malicious?

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

How do I remediate sgpakpubiz if I installed it?

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

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

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

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

Malicious package

sgpakpubizRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8616

Immediate action

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

gem uninstall sgpakpubiz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42eb87c9ae30d52b53665b35522c78bdce398e66ba2f4e8f232bed3321822fd9

7cd09b59537eeeff20047989e4a0cc43761e7b7b01b3a096cad3423aad35842b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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