Which versions of activestorage-redundancy are malicious?

The following RubyGems versions of activestorage-redundancy are flagged malicious: 90002.0. Treat any of these as compromised.

How do I remediate activestorage-redundancy if I installed it?

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

If activestorage-redundancy 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 activestorage-redundancy part of a known attack campaign?

Yes — activestorage-redundancy is associated with the RLMA-2025-06601 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 activestorage-redundancy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for activestorage-redundancy (version 90002.0).

Malicious package

activestorage-redundancyRubyGems

Advisory published Dec 23, 2025Updated Jul 23, 2026

activestorage-redundancy is a confirmed malicious RubyGems package (MAL-2025-192894) that executes malicious code on install (malicious version 90002.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in activestorage-redundancy (RubyGems)

MAL-2025-192894

Immediate action

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

gem uninstall activestorage-redundancy

Malicious versions

1 flagged

90002.0

Indicators of compromise (SHA-256)

be1b99093a5b27a1a7d4d4327b8297a1335c21ea7d7b0d30269e0035e696ecd4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for activestorage-redundancy (version 90002.0).
If you installed it — respond
Remove activestorage-redundancy 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 activestorage-redundancy 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. activestorage-redundancy on RubyGems has been identified as a malicious package (version 90002.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06601

Credits

ReversingLabs · finder

Detect & block this

O3 blocks activestorage-redundancy-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