Which versions of appfigures-client are malicious?

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

How do I remediate appfigures-client if I installed it?

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

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

Yes — appfigures-client is associated with the RLMA-2024-05441, RLUA-2024-09960 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 appfigures-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for appfigures-client (version 0.0.2).

Malicious package

appfigures-clientRubyGems

appfigures-client is a confirmed malicious RubyGems package (MAL-2024-6635) 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 appfigures-client (RubyGems)

MAL-2024-6635

Immediate action

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

gem uninstall appfigures-client

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

46bc6e762939441fa6988cb57b44005210b8bee1a719b4f9fbc36c76a47f3877

48d61227b01ad135517d99980302e8a6ed26486149c953d5b0e49df46013c6e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for appfigures-client (version 0.0.2).
If you installed it — respond
Remove appfigures-client 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 appfigures-client 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. appfigures-client 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-05441RLUA-2024-09960

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks appfigures-client-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