<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Llm-Agents on CuraSec</title><link>https://curasec.metacog.co.kr/tags/llm-agents/</link><description>Recent content in Llm-Agents on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 19:07:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/llm-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>ContextLeak: Malicious Tools Exfiltrate LLM Agent Runtime Context</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-contextleak-exfiltrating-llm-agent-context-via-malicious-too/</link><pubDate>Mon, 31 Aug 2026 19:07:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-contextleak-exfiltrating-llm-agent-context-via-malicious-too/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel research demonstrating that RL-crafted tool names and descriptions can coerce an LLM agent into leaking its full runtime context (prompt, trajectory, tool list) to an attacker endpoint; no PoC tooling or active exploitation reported, but teams building or integrating third-party tools into agent pipelines should treat tool metadata as an untrusted attack surface and audit how agents decide to pass context as arguments.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Purely academic research with no IOCs, ATT&amp;amp;CK mappings, or evidence of in-the-wild use; worth tracking as LLM agent deployments grow, but there is no detection or hunting action to take today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>ROPE: Provable Defense Against Indirect Prompt Injection in LLM Agents</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-rope-routed-origin-policy-enforcement-against-indirect-promp/</link><pubDate>Mon, 31 Aug 2026 19:07:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-rope-routed-origin-policy-enforcement-against-indirect-promp/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> ROPE introduces a structural origin-tracking approach that provably limits indirect prompt injection in tool-calling agents to under 3% success rate; worth evaluating if you are building or hardening LLM agent pipelines, but no running system change is required today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Provides useful framing on the attack surface of autonomous AI agents — relevant backdrop if your organization is evaluating AI agent deployments and building policy around permissible tool access.&lt;/li>
&lt;/ul></description></item><item><title>Diagnostic Framework for Long-Horizon Security LLM Agent Failures</title><link>https://curasec.metacog.co.kr/insights/2026-08-24-beyond-end-to-end-success-diagnosing-failures-in-long-horizo/</link><pubDate>Mon, 24 Aug 2026 13:10:29 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-24-beyond-end-to-end-success-diagnosing-failures-in-long-horizo/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Academic research introducing checkpoint-based diagnostics for multi-step security AI agents; relevant if you are building or evaluating agentic security tooling, but no immediate change to running systems is required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>LLM Agents Leak Protected Context via Tool-Call Argument Generation</title><link>https://curasec.metacog.co.kr/insights/2026-08-24-the-claws-in-plain-sight-unauthorized-context-disclosure-thr/</link><pubDate>Mon, 24 Aug 2026 13:10:29 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-24-the-claws-in-plain-sight-unauthorized-context-disclosure-thr/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Research demonstrates that prompt-level privacy policies fail to reliably prevent LLM agents from embedding protected attributes into generated tool-call arguments; if you ship agent pipelines, this motivates adding a purpose- and destination-aware inspection layer before tool execution, though no live exploit exists requiring an immediate change today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Novel disclosure vector where adversarial task context pressures agents into leaking protected fields via tool arguments — no IOCs, ATT&amp;amp;CK mappings, or active campaign to hunt for, but relevant background if your org monitors AI agent activity.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Controlled research showing prompt-level privacy guardrails in LLM agents are not a reliable enforcement boundary; useful context when developing AI governance policy for agent deployments, but no breach or regulation deadline requires immediate action.&lt;/li>
&lt;/ul></description></item><item><title>Memory Provenance Laundering: New Attack Class in LLM Agent Memory</title><link>https://curasec.metacog.co.kr/insights/2026-08-03-memory-provenance-laundering-in-llm-agents-a-non-amplificati/</link><pubDate>Mon, 03 Aug 2026 15:12:30 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-03-memory-provenance-laundering-in-llm-agents-a-non-amplificati/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Identifies a novel design flaw where LLM memory consolidation strips trust-level metadata from external inputs, letting injected content inherit user-level authority. No patch cycle applies yet, but teams building agentic systems with persistent memory should review their memory consolidation pipelines against this authority-amplification model.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, active exploitation, or detection surface currently exist; this is pre-deployment research. Worth tracking as AI agent adoption grows, as it describes an attack class that would be difficult to detect with existing SIEM/EDR tooling.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Establishes a concrete risk category for enterprise LLM agent deployments — memory subsystems can be poisoned to escalate trust silently. Useful framing for AI governance discussions, but no vendor exposure or regulatory deadline triggers action this quarter.&lt;/li>
&lt;/ul></description></item><item><title>CARE: Static pre-execution verifier for LLM agent shell commands</title><link>https://curasec.metacog.co.kr/insights/2026-07-27-care-pre-execution-command-verification-for-shell-executing/</link><pubDate>Mon, 27 Jul 2026 15:10:27 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-27-care-pre-execution-command-verification-for-shell-executing/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel static-analysis approach to sandboxing LLM-generated shell commands before execution; worth evaluating if you&amp;rsquo;re building or securing agentic pipelines, but no patch or config action required today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Useful framing for AI-agent risk governance — highlights that shell-executing LLM agents need formal pre-execution controls, relevant when developing policy for agentic AI tooling adoption.&lt;/li>
&lt;/ul></description></item><item><title>Mandiant: Blueprint for AI-Assisted Vulnerability Management Guardrails</title><link>https://curasec.metacog.co.kr/insights/2026-07-17-demystifying-ai-exploits-a-blueprint-for-ai-assisted-vulnera/</link><pubDate>Fri, 17 Jul 2026 12:06:10 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-17-demystifying-ai-exploits-a-blueprint-for-ai-assisted-vulnera/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Practical architectural framing for safely embedding LLM agents into CI/CD and vuln-discovery pipelines; worth reviewing before deploying privileged AI agents, but no immediate patch or config action required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The M-Trends 2026 finding that mean time-to-exploit has turned negative (−7 days) is useful framing for board risk discussions and for justifying investment in AI-accelerated detection; no immediate action required, but the data point belongs in the next risk briefing.&lt;/li>
&lt;/ul></description></item></channel></rss>