<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Agents on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ai-agents/</link><description>Recent content in Ai-Agents on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 11:49:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Ghostcommit: image-hidden prompt injection fools AI code review agents</title><link>https://curasec.metacog.co.kr/insights/2026-07-11-ghostcommit-hides-prompt-injection-in-images-to-fool-ai-agen/</link><pubDate>Sat, 11 Jul 2026 11:49:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-11-ghostcommit-hides-prompt-injection-in-images-to-fool-ai-agen/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Research-grade but practical: any AI coding agent with access to .env or secrets files is a potential exfiltration path via a malicious image in a PR. Audit what filesystem scope your AI code-review agents hold, and restrict or deny access to credential files and secret stores.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Novel TTP — prompt injection embedded in images bypasses AI reviewers that never inspect image content, then coerces coding agents into exfiltrating secrets. No active exploitation or IOCs reported; file for future detection work around anomalous AI-agent file reads.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Demonstrates that AI coding-agent tools carry unchecked secret-exfiltration risk through a non-obvious vector. Before broader AI agent adoption, establish a policy governing what repository paths and credentials these tools may access, and confirm existing vendor tools have equivalent controls.&lt;/li>
&lt;/ul></description></item><item><title>Identity Risks in AI Agent Deployments — CrowdStrike Analysis</title><link>https://curasec.metacog.co.kr/insights/2026-07-11-the-identity-problem-hiding-in-ai-agent-deployments/</link><pubDate>Sat, 11 Jul 2026 11:49:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-11-the-identity-problem-hiding-in-ai-agent-deployments/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> AI agent identity risks (non-human identities, credential sprawl, OIDC/service account misuse) are an emerging design concern worth factoring into how agentic workloads are architected, but no patch or immediate action is indicated.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Understanding how AI agents acquire and use credentials could inform future detection logic around anomalous non-human identity activity, but no IOCs or TTPs are provided here.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If your org is deploying AI agents, review whether your identity governance policies cover non-human agent credentials — this is a quarter-horizon policy gap before it becomes a control gap.&lt;/li>
&lt;/ul></description></item></channel></rss>