Which versions of moving-images are malicious?

The following RubyGems versions of moving-images are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate moving-images if I installed it?

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

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

Yes — moving-images is associated with the RLMA-2024-05797, RLUA-2024-10318, RLUA-2026-08602 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 moving-images across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for moving-images (version 1.0.1).

Malicious package

moving-imagesRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

moving-images is a confirmed malicious RubyGems package (MAL-2024-6991) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in moving-images (RubyGems)

MAL-2024-6991

Immediate action

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

gem uninstall moving-images

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

843003ed8b7a77551b3d33caa4087841caafc17b0635902ec9b61c7da0b08104

20b84b20865d2810d574cc962ac736c627186b2edeabfa8eeb43a9b86b7521d9

4d217f57de04e77fd9b76d977759627cdb786c99c836e3ff3eb5ea5663a0561f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05797RLUA-2024-10318RLUA-2026-08602

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks moving-images-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