Malware in ai-sdk-ollama
Malware discovered in the ai-sdk-ollama npm package. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with ai-sdk-ollama installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ai-sdk-ollamanpm package
A critical malware incident has been identified in the ai-sdk-ollama npm package. According to the GitHub Security Advisory (GHSA-m9j7-x8ww-5jwr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package compromise.\n\nThis is a supply chain attack affecting the npm ecosystem through a compromised package in the AI/LLM tooling space.
Indicators of compromise
- Packages
- ai-sdk-ollama
Remediation
- Immediately isolate any system with ai-sdk-ollama installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the ai-sdk-ollama package from all affected systems
- Perform a full security audit and malware scan on all affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Update to a patched version of ai-sdk-ollama once available and verified as safe
Sources
- GitHub Advisory GHSA-m9j7-x8ww-5jwr · GitHub Advisory Database
Cite this entry
"Malware in ai-sdk-ollama." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-ai-sdk-ollama-18ubxd
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in zyr-agent (npm)
zyr-agent (npm) shipped with malicious code that enables remote command execution through a hardcoded preview-slug endpoint controlled by the package author. The AI agent auto-executes tool calls (including bash commands) returned by the remote endpoint without user confirmation.
npmAI agents & skillsMalicious commitCompromised package - resolvedcritical
Malicious code in @lyxa.ai/core (npm)
The npm package @lyxa.ai/core contained malicious code that unconditionally routes all application events through author-controlled cloud infrastructure (CloudAMQP, Redis Cloud, GCP) using embedded credentials, and ships live private keys for GCP and Firebase services, allowing the author to intercept, modify, and trigger arbitrary handlers in any installer's process.
npmAI agents & skillsCompromised packageMalicious maintainer - resolvedcritical
Malicious code in mangomind-agent (npm)
The npm package mangomind-agent contained malicious code that established a persistent WebSocket connection to a hardcoded relay server, enabling remote code execution and AI-agent-driven filesystem access on any host running the package. The vulnerability was discovered and reported by the OpenSSF.
npmAI agents & skillsCompromised packageMalicious commit - resolvedcritical
Malicious code in @aster110/cc2wechat (npm)
The npm package @aster110/cc2wechat contains malicious code that establishes a remote shell interface via WeChat messages. When the daemon is started, it polls Tencent's iLink Bot API and forwards incoming WeChat messages to locally-hosted AI agents (Claude or Codex) configured with safety gates disabled, allowing arbitrary shell and filesystem operations.
npmAI agents & skillsCompromised package