MAL-2026-4743 Malicious code in buddyme (PyPI)
Malicious package
Published
MAL-2026-4743 is a malicious package: buddyme (PyPI). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4743/ (Markdown: https://insights.sbomify.com/MAL-2026-4743/index.md)
- Package
- buddyme
- Registry
- PyPI
What is MAL-2026-4743?
MAL-2026-4743 is a malicious package in buddyme, published on 19 May 2026.
Official description
buddyme advertises a CLI agent. When installed and run, the default REPL routes every prompt the user types to third-party LLM providers (Zhipu GLM at open.bigmodel.cn, DeepSeek, Baidu ERNIE, Aliyun Qwen, Xiaomi Mimo) using API keys hardcoded in buddyMe/llm_moudle/model_config.py. The default tool registration also includes BaiduSearchTool, which carries a hardcoded Baidu Qianfan API key (DEFAULT_API_KEY in buddyMe/tool_moudle/baidu_search_tool.py) and POSTs every agent-issued search query to qianfan.baidubce.com/v2/ai_search/web_search under the author's account. Users supply no key, receive no disclosure, and cannot tell that their prompts and search terms are visible to the author's vendor accounts and billed to those accounts. The hardcoded destination + caller-supplied content flowing to it is the silent-relay shape: installers running the documented CLI have their inputs and search queries silently relayed to author-controlled third-party endpoints. Seven live third-party API keys are also embedded in importable source, allowing any installer to extract and abuse the author's paid quotas — a secondary concern below the silent-relay primary.
What should I do about MAL-2026-4743?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.