<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Social-Engineering on AI Watchtower</title>
    <link>https://aleph-beth.github.io/AI-Watchtower/tags/social-engineering/</link>
    <description>Recent content in Social-Engineering on AI Watchtower</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://aleph-beth.github.io/AI-Watchtower/tags/social-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When the Guards Are Agents Too: The Recursive Corruption of Control Systems</title>
      <link>https://aleph-beth.github.io/AI-Watchtower/posts/2026-06-30-recursive-corruption-of-ai-control-systems/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://aleph-beth.github.io/AI-Watchtower/posts/2026-06-30-recursive-corruption-of-ai-control-systems/</guid>
      <description>Classic security tools hunt for dangerous words: &amp;lsquo;hack&amp;rsquo;, &amp;lsquo;bomb&amp;rsquo;, &amp;lsquo;urgent&amp;rsquo;. But you don&amp;rsquo;t subvert an AI agent with suspicious vocabulary — you subvert it with the ordinary language of the business: a role, a process, a plausible emergency. And when the agent that monitors, the SIEM that correlates and the auditor that checks are themselves AI agents, the attacker no longer has to defeat a system: it corrupts them in a chain. This article explains that recursive-corruption mechanism and what a decision-maker must demand to break it.</description>
    </item>
  </channel>
</rss>
