Which versions of piko-fast-box are malicious?

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

How do I remediate piko-fast-box if I installed it?

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

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

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

Search your lockfiles and build artifacts for piko-fast-box (version 0.0.1).

Malicious package

piko-fast-boxRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

piko-fast-box is a confirmed malicious RubyGems package (MAL-2026-15766) 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-fast-box (RubyGems)

MAL-2026-15766

Immediate action

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

gem uninstall piko-fast-box

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1a981ecf18c1336a7b247a306982e9fc33a735a369dc1bdd6e6dfaa32567d18f

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks piko-fast-box-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