Which versions of activerecord-globalize are malicious?

The following RubyGems versions of activerecord-globalize are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate activerecord-globalize if I installed it?

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

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

Yes — activerecord-globalize is associated with the RLMA-2024-05275, RLUA-2024-09794 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 activerecord-globalize across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for activerecord-globalize (version 1.0.0).

Malicious package

activerecord-globalizeRubyGems

activerecord-globalize is a confirmed malicious RubyGems package (MAL-2024-6469) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in activerecord-globalize (RubyGems)

MAL-2024-6469

Immediate action

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

gem uninstall activerecord-globalize

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b7e9320be400a205abaccc27bba705203625f63decc405ead39fcfecdf2bf968

05e466139dfa1877110219c1d88a5a989898fe65167ebc549e4b6c71138592ee

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05275RLUA-2024-09794

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks activerecord-globalize-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