Which versions of buinxler are malicious?

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

How do I remediate buinxler if I installed it?

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

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

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

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

Malicious package

buinxlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buinxler (RubyGems)

MAL-2026-16799

Immediate action

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

gem uninstall buinxler

Malicious versions

2 flagged

1.0.01.0.68994

Indicators of compromise (SHA-256)

27a2983ca2dbb3cd2b4d386ba1230f2bdb8fcf3610deba7edf77854072a92856

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07484

Credits

ReversingLabs · finder

Detect & block this

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