Which versions of acts-as_publicable are malicious?

The following RubyGems versions of acts-as_publicable are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate acts-as_publicable if I installed it?

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

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

Yes — acts-as_publicable is associated with the RLMA-2024-05306, RLUA-2024-09825 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 acts-as_publicable across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for acts-as_publicable (version 0.0.4).

Malicious package

acts-as_publicableRubyGems

acts-as_publicable is a confirmed malicious RubyGems package (MAL-2024-6500) that executes malicious code on install (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in acts-as_publicable (RubyGems)

MAL-2024-6500

Immediate action

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

gem uninstall acts-as_publicable

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

fd9235e96cc5ecbf02306886a39f69c5b43b348c18765f6de54302a64176a149

b4ef550f97e01abbe90f12debb430215685eeae2a5887277ec527e36fdbc1520

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05306RLUA-2024-09825

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks acts-as_publicable-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