Which versions of agfosscab20 are malicious?

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

How do I remediate agfosscab20 if I installed it?

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

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

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

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

Malicious package

agfosscab20RubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

agfosscab20 is a confirmed malicious RubyGems package (MAL-2026-7474) 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 agfosscab20 (RubyGems)

MAL-2026-7474

Immediate action

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

gem uninstall agfosscab20

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7f48fdd876d047feac251302856a04ef295c1275e3c4e3a0328cdfe30a4d925d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for agfosscab20 (version 0.0.1).
If you installed it — respond
Remove agfosscab20 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 agfosscab20 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. agfosscab20 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-02125

Credits

ReversingLabs · finder

Detect & block this

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