Paperclip AI Flaws Let Attackers Run Host Commands via Malicious Agent Imports

Two security flaws in Paperclip could let attackers execute commands on a network server or a developer's computer. Paperclip is an open-source control plane for teams of artificial intelligence (AI) agents, and both paths rely on importing a malicious agent and starting it. A third flaw could expose sensitive data and control-plane details through application programming interface (API) routes

According to multiple advisories, Paperclip AI suffers from critical vulnerabilities that allow attackers to execute arbitrary OS commands on the Paperclip server host or developers’ machines by importing and running malicious agents, including unauthenticated RCE in default authenticated-mode deployments.[1][4][9][10] Reports also describe information disclosure flaws that expose sensitive agent metadata and control-plane details via API routes.[1][3][5] From a RealGround perspective, this illustrates high-risk AI agent abuse and AI supply chain exposure: importing untrusted agents becomes an execution path to the host, and weak isolation between agents, tenants, and API surfaces turns orchestration logic into an attack vector. Practically, organizations should treat agent import flows as remote code execution surfaces, enforce strict authentication/authorization around agent lifecycle operations, continuously red-team agent orchestration APIs, and inventory/pin third-party agent dependencies as part of an AI SBOM to reduce compromise via malicious or tampered agents.