Which versions of nano-smart-pkg are malicious?

The following RubyGems versions of nano-smart-pkg are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate nano-smart-pkg if I installed it?

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

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

Yes — nano-smart-pkg is associated with the RLMA-2026-05728 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 nano-smart-pkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nano-smart-pkg (version 0.0.1).

Malicious package

nano-smart-pkgRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

nano-smart-pkg is a confirmed malicious RubyGems package (MAL-2026-15762) 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 nano-smart-pkg (RubyGems)

MAL-2026-15762

Immediate action

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

gem uninstall nano-smart-pkg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff85ba20e3452a5e66469f1bd093c473866c092d4ab427aeabb2b5c2fe1f7bb5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nano-smart-pkg (version 0.0.1).
If you installed it — respond
Remove nano-smart-pkg 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 nano-smart-pkg 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. nano-smart-pkg 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-05728

Credits

ReversingLabs · finder

Detect & block this

O3 blocks nano-smart-pkg-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