Which versions of abunxler are malicious?

The following RubyGems versions of abunxler are flagged malicious: 1.0.0, 1.0.1863. Treat any of these as compromised.

How do I remediate abunxler if I installed it?

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

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

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

Search your lockfiles and build artifacts for abunxler (2 malicious versions).

Malicious package

abunxlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

abunxler is a confirmed malicious RubyGems package (MAL-2026-16551) that executes malicious code on install (malicious versions 1.0.0, 1.0.1863). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abunxler (RubyGems)

MAL-2026-16551

Immediate action

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

gem uninstall abunxler

Malicious versions

2 flagged

1.0.01.0.1863

Indicators of compromise (SHA-256)

894912bf82915b8f0343e563ae5787ed4db285967777bc07ca20338775dd6ef8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-06693

Credits

ReversingLabs · finder

Detect & block this

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