<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Agent on CuraSec</title><link>https://curasec.metacog.co.kr/tags/multi-agent/</link><description>Recent content in Multi-Agent on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 15:04:44 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/multi-agent/index.xml" rel="self" type="application/rss+xml"/><item><title>Threat Actors Adopt AI Multi-Agent Frameworks for Credential Theft</title><link>https://curasec.metacog.co.kr/insights/2026-09-08-hackers-build-ai-frameworks-for-widescale-credential-theft/</link><pubDate>Tue, 08 Sep 2026 15:04:44 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-08-hackers-build-ai-frameworks-for-widescale-credential-theft/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> No specific vulnerability or patch here, but AI-automated attack pipelines increase the velocity and scale of credential stuffing — worth reviewing whether MFA enforcement and credential-exposure monitoring cover your current gaps.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Multi-agent automation of attack stages signals higher-volume, lower-dwell-time credential campaigns; plan to tune authentication anomaly detections (burst login attempts, impossible travel) and evaluate whether existing rules handle AI-paced credential stuffing rates.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AI-enabled attack automation is a strategic trend useful for board-level risk narrative and future AI-threat policy discussions, but no specific vendor breach or regulation deadline makes immediate action necessary.&lt;/li>
&lt;/ul></description></item></channel></rss>