Which versions of algolia-places are malicious?

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

How do I remediate algolia-places if I installed it?

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

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

Yes — algolia-places is associated with the RLMA-2024-05363, RLUA-2024-09882 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 algolia-places across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for algolia-places (version 0.1.2).

Malicious package

algolia-placesRubyGems

algolia-places is a confirmed malicious RubyGems package (MAL-2024-6557) 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 algolia-places (RubyGems)

MAL-2024-6557

Immediate action

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

gem uninstall algolia-places

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

002c85d2815a4e4f977c01c8aba48841f6df5ab66e484423d5ee857a8a9d41d5

b5742d0e274609fb11dab50de0970d409438517dd73fd5f60d70596c88978ed1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for algolia-places (version 0.1.2).
If you installed it — respond
Remove algolia-places 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 algolia-places 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. algolia-places 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-05363RLUA-2024-09882

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks algolia-places-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