Which versions of indonesian-province are malicious?

The following RubyGems versions of indonesian-province are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate indonesian-province if I installed it?

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

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

Yes — indonesian-province is associated with the RLMA-2024-05752, RLUA-2024-10271, RLUA-2026-08232 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 indonesian-province across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for indonesian-province (version 0.0.2).

Malicious package

indonesian-provinceRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

indonesian-province is a confirmed malicious RubyGems package (MAL-2024-6946) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in indonesian-province (RubyGems)

MAL-2024-6946

Immediate action

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

gem uninstall indonesian-province

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

50c9d81dea9db92cf714473783b603091973d916b1a9a24b2a82afb20cbf27e1

18145ab758651248588743de6b17cb3e86d75638f9a8e4664c3221254937cd68

fcf5ac87e5106dc600982eb00d2ed9b09708a4ee8cf55fbf273cd02d76935b44

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05752RLUA-2024-10271RLUA-2026-08232

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks indonesian-province-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