Which versions of city-search are malicious?

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

How do I remediate city-search if I installed it?

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

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

Yes — city-search is associated with the RLMA-2024-05637, RLUA-2024-10156, RLUA-2026-07928 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 city-search across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for city-search (version 0.0.4).

Malicious package

city-searchRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

city-search is a confirmed malicious RubyGems package (MAL-2024-6831) 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 city-search (RubyGems)

MAL-2024-6831

Immediate action

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

gem uninstall city-search

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

1bbe0e348a8390c3af2f274974d34033eb1fd89446ff3a067acd6918398a6bbe

29140d83044a601f0f95972d09b055d863c735aadc4f95ab8c476a388c4152f9

7273cf760ae1eba499ed7b937501ccaae851d610a060c429d82b6e0540119d39

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for city-search (version 0.0.4).
If you installed it — respond
Remove city-search 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 city-search 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. city-search 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-05637RLUA-2024-10156RLUA-2026-07928

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks city-search-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