Which versions of piko-clean-mod are malicious?

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

How do I remediate piko-clean-mod if I installed it?

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

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

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

Search your lockfiles and build artifacts for piko-clean-mod (version 0.0.1).

Malicious package

piko-clean-modRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

piko-clean-mod is a confirmed malicious RubyGems package (MAL-2026-15765) 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-clean-mod (RubyGems)

MAL-2026-15765

Immediate action

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

gem uninstall piko-clean-mod

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e04c2a5ff476d062745988f728f5c1b575c28876e4eedcfce43a21ed75c43423

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks piko-clean-mod-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