Which versions of bundlnef are malicious?

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

How do I remediate bundlnef if I installed it?

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

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

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

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

Malicious package

bundlnefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlnef (RubyGems)

MAL-2026-16988

Immediate action

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

gem uninstall bundlnef

Malicious versions

2 flagged

1.0.01.0.35570

Indicators of compromise (SHA-256)

a117969eccd72f37e97ab12be69eb83d1772974a493e2b58735446f225f324a1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07674

Credits

ReversingLabs · finder

Detect & block this

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