Which versions of piko-sharp-sys are malicious?

The following RubyGems versions of piko-sharp-sys are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate piko-sharp-sys if I installed it?

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

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

Yes — piko-sharp-sys is associated with the RLMA-2026-05739 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 piko-sharp-sys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for piko-sharp-sys (version 0.0.1).

Malicious package

piko-sharp-sysRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

piko-sharp-sys is a confirmed malicious RubyGems package (MAL-2026-15773) 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 piko-sharp-sys (RubyGems)

MAL-2026-15773

Immediate action

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

gem uninstall piko-sharp-sys

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

589e327fe8232ca317a399ca9b6054926ac5e104ed5a0a5ddf1049a532dc3b9c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for piko-sharp-sys (version 0.0.1).
If you installed it — respond
Remove piko-sharp-sys 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 piko-sharp-sys 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. piko-sharp-sys 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-05739

Credits

ReversingLabs · finder

Detect & block this

O3 blocks piko-sharp-sys-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