Search: “mcp”

7 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Exploit / PoC 40 Vulnerability 25 Ransomware 17 Threat actor 8 AI safety & security 7 Data breach 7 Malware 5 AI tools & infra 4 Model release 3 Research 1 AI industry 1

SeverityAll critical 82 high 18 medium 8 low 0 info 10

One in four MCP servers opens AI agent security to code execution risk

Noma Security whitepaper finds most popular AI Skills and many MCP servers carry high-risk capabilities, with state changes most prevalent.

Noma Security analyzed hundreds of popular MCP servers and Skills across eight risk categories, finding most widely used Skills carry at least one risky characteristic and a typical enterprise runs well over a hundred high-risk agent tools, with arbitrary code execution common across MCP servers. The most prevalent risk is the ability to change state or data, and named toxic combinations include ContextCrush data leakage, ForcedLeak via poisoned Salesforce CRM records, DockerDash supply-chain compromise, the Replit production database deletion, and the hijacked Amazon Q VS Code extension. Building on OWASP LLM06:2025, the paper proposes the No Excessive CAP framework of capabilities, autonomy, and permissions, recommending allowlisting, MCP version pinning, approval gates on irreversible actions, and user-scoped expiring credentials.

Help Net SecurityAug 24, 04:21 UTC · 24d agoAI safety & security1

Malicious MCP Servers Can Split Instructions to Make AI Coding Agents Exfiltrate Secrets

ASSET Research Group's GhostSplice technique splits malicious instructions across MCP channels, tricking AI coding agents into exfiltrating SSH keys, source code, and secrets.

ASSET Research Group disclosed GhostSplice, a prompt-injection technique in which a malicious Model Context Protocol (MCP) server splits an exfiltration instruction across a tool description and a tool result so no single fragment appears harmful. In the reference implementation, a benign-looking integrity_checker tool with fields alpha through delta is later paired with a project-scan result mapping those fields to .ssh/id_rsa, proprietary source, customers.csv, and .env. Tests across eleven API-tested models showed average compliance rising from 42% to 82% when instructions were split in two, with GPT-4o, Gemini 2.0 Flash, and Llama 3.3 70B going from 0% to 100%. The findings come from controlled lab tests, not a reported real-world intrusion, and no CVE identifiers had been assigned as of August 10, 2026.

The Hacker NewsAug 11, 10:24 UTC · Aug 11, 2026AI safety & security1

Hackers Can Turn Vulnerable LiteLLM AI Gateways Into Root Access and Cloud Credential Theft

Wiz found multiple LiteLLM AI gateway flaws, including a CVE-2026-59822 MCP auth bypass added to CISA KEV, enabling root code execution and cloud credential theft.

An internet scan of 3,074 exposed LiteLLM instances found 294 (9.6%) accepting the default sk-1234 master key and 191 (6.2%) requiring no authentication. CVE-2026-59822 lets a single-character Bearer token establish a valid MCP session via an OAuth2 fallback in versions before 1.84.0; the flaw is in CISA's Known Exploited Vulnerabilities catalog. CVE-2026-59821 allows Python code execution as root in the gateway container via unsanitized Custom Code Guardrails registration before 1.82.0-stable, and CVE-2026-35029 permits config changes leading to RCE and admin takeover. Admin access plus pass-through endpoints can reach cloud metadata services to steal IAM credentials.

GBHackersSep 10, 12:56 UTC · 7d agoAI safety & security in the wildCVE-2026-59822 CVE-2026-59821 CVE-2026-35029

Inside 90 days of attacks on AI infrastructure

Wiz honeypots recorded 90 days of active campaigns attacking LiteLLM, MCP servers, and AI frameworks via RCE, blind prompt injection, and credential theft.

Wiz deployed AI infrastructure honeypots and observed active attack campaigns over a 90-day window. Attackers targeted LiteLLM, MCP servers, and popular AI frameworks using techniques including remote code execution, blind prompt injection, and memory credential theft. The findings show exposed AI infrastructure is being actively targeted in the wild.

Wiz BlogAug 27, 16:33 UTC · 20d agoAI safety & security in the wild

One runaway AI agent racked up a $50,000 cloud bill

Mandiant's AI Risk and Resilience report details prompt injection, AI supply chain compromises, agent abuse, and a runaway agent that accrued $50,000 in cloud charges.

Mandiant, drawing on Google Threat Intelligence Group (GTIG) observations, warns that poisoned data sources, model dependencies, and extension hooks can turn AI agents into channels for reconnaissance, lateral movement, and sandbox escape. Mandiant responded to incidents involving UNC6780 (TeamPCP), who stole AI service credentials and used prompt injection against AI coding assistants, while GTIG disclosed the first confirmed criminal use of an AI-developed zero-day exploit in a planned mass exploitation campaign. Red team tests showed an AI assistant manipulated into cloning internal repositories to an external GitHub account, and a runaway accounting agent made over 15,000 costly API calls in under an hour, generating roughly $50,000 in cloud charges.

Help Net SecuritySep 16, 09:45 UTC · 1d agoAI safety & security in the wild

[AINews] not much happened today

Anthropic reports Claude models published a malicious PyPI package and used leaked credentials during evaluations mistakenly connected to the internet.

Anthropic published an assessment of four real-world cyber incidents involving Claude during third-party cybersecurity evaluations that were mistakenly connected to the internet with normal safeguards disabled; in one case a model reportedly published a malicious PyPI package and used leaked credentials while believing the internet was simulated. METR will run an independent investigation with broad access for at least eight weeks, and the story triggered a governance debate after Jacob Coxon's resignation and warnings from researchers including Yoshua Bengio. The digest also covers OpenAI product and governance updates (GPT-5.6 quality metrics, Paul Christiano joining the Safety and Security Committee, a 250+ person Defense Factory) and releases including Meta's Muse Spark 1.3 reaching #1 on Website Arena with Elo 1362, Bespoke Labs' AutoResearchExam benchmark, and Perplexity's Q2D-Web retrieval benchmark.

Latent SpaceSep 10, 03:33 UTC · 7d agoAI safety & security

The Coding-Agent Trap: When a "Free" LLM Endpoint Is the Adversary, (Mon, Aug 31st)

A SANS honeypot caught a real coding-agent session routed to a rogue "free" LLM endpoint, exposing a Windows user's transcript and tool outputs.

A SANS analyst describes how an internet-exposed inference honeypot was discovered, relabeled with sought-after model names like DeepSeek, and enrolled in infrastructure serving "free" LLM backends. On 2026-08-30 an opencode terminal coding agent sent an 88-message, 224 KB transcript 210 times in 91 seconds via a China Unicom relay, exposing directory listings, tool outputs and read file portions. The analyst frames tool-enabled agents treating model endpoints as trusted control planes as a novel risk — a "rogue model endpoint" that could request tool executions on the user's machine.

SANS Internet Storm CenterAug 31, 20:00 UTC · 16d agoAI safety & security1