Which versions of bunldet are malicious?

The following RubyGems versions of bunldet are flagged malicious: 1.0.58081. Treat any of these as compromised.

How do I remediate bunldet if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldet (version 1.0.58081).

Malicious package

bunldetRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunldet is a confirmed malicious RubyGems package (MAL-2026-17069) that executes malicious code on install (malicious version 1.0.58081). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunldet (RubyGems)

MAL-2026-17069

Immediate action

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

gem uninstall bunldet

Malicious versions

1 flagged

1.0.58081

Indicators of compromise (SHA-256)

279bba56ce9df8466766a4723ec800e99a20845c97c9bb4833603a390de3774b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07755

Credits

ReversingLabs · finder

Detect & block this

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