Which versions of benign200012 are malicious?

The following RubyGems versions of benign200012 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate benign200012 if I installed it?

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

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

Yes — benign200012 is associated with the RLMA-2026-02195 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 benign200012 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for benign200012 (version 0.0.1).

Malicious package

benign200012RubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

benign200012 is a confirmed malicious RubyGems package (MAL-2026-7544) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in benign200012 (RubyGems)

MAL-2026-7544

Immediate action

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

gem uninstall benign200012

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1267fab47d76064fababac12a0c4c1bf9baf3ce526b1134ecf11e3db121a8660

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02195

Credits

ReversingLabs · finder

Detect & block this

O3 blocks benign200012-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