Which versions of auto-flick are malicious?

The following RubyGems versions of auto-flick are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate auto-flick if I installed it?

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

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

Yes — auto-flick is associated with the RLMA-2024-05533, RLUA-2024-10052 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 auto-flick across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for auto-flick (version 0.1.2).

Malicious package

auto-flickRubyGems

auto-flick is a confirmed malicious RubyGems package (MAL-2024-6727) that executes malicious code on install (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in auto-flick (RubyGems)

MAL-2024-6727

Immediate action

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

gem uninstall auto-flick

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

2fb34499c25bc07c6395cf7d0eb0c89531274e675e98cc0744d33a7d2c8c0874

7f1bfb36de1262a100cc0df8baf2c996aee2c3cfd57151fb44d2477ce61a151f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05533RLUA-2024-10052

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks auto-flick-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