Which versions of ultra-safe-box are malicious?

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

How do I remediate ultra-safe-box if I installed it?

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

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

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

Search your lockfiles and build artifacts for ultra-safe-box (version 0.0.1).

Malicious package

ultra-safe-boxRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

ultra-safe-box is a confirmed malicious RubyGems package (MAL-2026-15804) 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 ultra-safe-box (RubyGems)

MAL-2026-15804

Immediate action

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

gem uninstall ultra-safe-box

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

332e369688001a3624f65428511ca3ef03f006d75d42aa7d684e6eb86800abfc

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ultra-safe-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