Which versions of a0a_arcgraph are malicious?

The following RubyGems versions of a0a_arcgraph are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate a0a_arcgraph if I installed it?

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

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

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

Search your lockfiles and build artifacts for a0a_arcgraph (4 malicious versions).

Malicious package

a0a_arcgraphRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

a0a_arcgraph is a confirmed malicious RubyGems package (MAL-2026-7469) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in a0a_arcgraph (RubyGems)

MAL-2026-7469

Immediate action

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

gem uninstall a0a_arcgraph

Malicious versions

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

a4e4293fed639f06e3eec8cc74435cac11ff8361a1a848abba9c5bdfa08b431e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02120

Credits

ReversingLabs · finder

Detect & block this

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