Which versions of movingsign-api are malicious?

The following RubyGems versions of movingsign-api are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate movingsign-api if I installed it?

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

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

Yes — movingsign-api is associated with the RLMA-2024-05799, RLUA-2024-10320, RLUA-2026-08604 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 movingsign-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for movingsign-api (version 0.0.2).

Malicious package

movingsign-apiRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

movingsign-api is a confirmed malicious RubyGems package (MAL-2024-6993) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in movingsign-api (RubyGems)

MAL-2024-6993

Immediate action

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

gem uninstall movingsign-api

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

71193f71a2b66cd30052d2a8998371c6082a9e5187b686481bda6f408cd72cbd

7fdf350fc6420098a65b66633b6263b7fa47cb8affc30756728067f7af4223af

89615cfc6414fa6bdb20785134124b8e04da77a0a3dbf8083621512cb58b0412

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05799RLUA-2024-10320RLUA-2026-08604

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks movingsign-api-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