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

efghr-honeybee-sdkPyPI

Malicious code in efghr-honeybee-sdk (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2005
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall efghr-honeybee-sdk

What this malware does

During installation, package attempts to modify LLM configuration files to provide a backdoor instruction for further control over an AI agent.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-flyio-token-client-efgh

Reasons (based on the campaign):

  • llm-threat

  • The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged
0.1.00.2.0

Indicators of compromise (SHA-256)

e77e2d0088390e5dc421f70a65ade331bfbf554afcc9cc42362098d0ed130692

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    efghr-honeybee-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If efghr-honeybee-sdk 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 efghr-honeybee-sdk 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. efghr-honeybee-sdk on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-flyio-token-client-efgh

References

Credits

  • Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks efghr-honeybee-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

efghr-honeybee-sdk (PyPI) malicious package — MAL-2026-2005 | O3 Security