Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

queenbee-pluginRubyGems

Malicious code in queenbee-plugin (RubyGems) Remove it immediately and rotate any exposed credentials.

MAL-2025-192914
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall queenbee-plugin

What this malware does

The OpenSSF Package Analysis project identified 'queenbee-plugin' @ 99.0.7 (rubygems) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

9 flagged
99.0.099.0.199.0.399.0.499.0.599.0.699.0.799.0.890002.0

Indicators of compromise (SHA-256)

d90da20fcb1e0c7e7aca86ec48a7866d2263fe80dd2698b692fe426ae4de8382
705c314b786f674b8b06825a6211d1595db25022404041a4d8760b4094e863e1
cd8daaa01f0acf4635ceb03645a039723dca0f1c74a1f3b56023a29b8a146637

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for queenbee-plugin (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging queenbee-plugin across your stack and pipelines.

  2. If you installed it — respond

    Remove queenbee-plugin 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.

  3. Did it already run?

    If queenbee-plugin was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks queenbee-plugin before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. queenbee-plugin on RubyGems has been identified as a malicious package (versions 99.0.0, 99.0.1, 99.0.3, 99.0.4, 99.0.5, 99.0.6, 99.0.7, 99.0.8, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06624RLUA-2026-02090

Credits

  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks queenbee-plugin-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.

queenbee-plugin (RubyGems) malicious package — MAL-2025-192914 | O3 Security