<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web-Attacks on CuraSec</title><link>https://curasec.metacog.co.kr/tags/web-attacks/</link><description>Recent content in Web-Attacks on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 Oct 2026 16:37:36 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/web-attacks/index.xml" rel="self" type="application/rss+xml"/><item><title>Autonomous AI agents attempted to hack US/Canadian government websites</title><link>https://curasec.metacog.co.kr/insights/2026-10-02-autonomous-ai-agents-tried-to-hack-us-canadian-government-we/</link><pubDate>Fri, 02 Oct 2026 16:37:36 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-02-autonomous-ai-agents-tried-to-hack-us-canadian-government-we/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Illustrates AI-driven autonomous attack tooling probing web properties for data extraction; no specific CVE or affected software identified, but useful context for hardening rate-limiting and access controls on public-facing endpoints.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, no ATT&amp;amp;CK mapping, and no detection artifacts are provided; the technique is worth tracking as AI-automated reconnaissance matures, but there is nothing actionable to hunt or detect today.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Demonstrates AI agents being weaponized for autonomous web probing — relevant background for emerging AI-threat policy discussions, but no vendor exposure or regulatory trigger requires immediate leadership action.&lt;/li>
&lt;/ul></description></item></channel></rss>