<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>defensive.works Weekly Recon</title>
    <link>https://defensive.works/</link>
    <description>Weekly security recon across cloud, agents, and supply chain. One attack, one rule, one defender move. Five minutes, every Tuesday.</description>
    <language>en-us</language>
    <atom:link href="https://defensive.works/rss.xml" rel="self" type="application/rss+xml" />

    <item>
      <title>Weekly Recon #5: Trust the folder, start the process.</title>
      <link>https://defensive.works/recon/p/005</link>
      <guid isPermaLink="true">https://defensive.works/recon/p/005</guid>
      <pubDate>Tue, 19 May 2026 12:00:00 +0000</pubDate>
      <description>A malicious repo can now turn one trust prompt in a coding CLI into native code execution, Dev Tunnels are much closer to remote access software than a harmless forwarder, and the tooling around agent runtime visibility is finally starting to catch up. This issue is about convenience features that quietly became execution surfaces.</description>
    </item>

    <item>
      <title>Weekly Recon #4: The patch window closed. The registry pushed back.</title>
      <link>https://defensive.works/recon/p/004</link>
      <guid isPermaLink="true">https://defensive.works/recon/p/004</guid>
      <pubDate>Tue, 12 May 2026 12:00:00 +0000</pubDate>
      <description>LiteLLM went from GitHub Advisory Database index to honeypot exploitation in 36 hours, pnpm 11 added a 24-hour default delay before brand-new packages resolve, and the Context.ai to Vercel chain showed why OAuth grants need the same default friction as package installs.</description>
    </item>

    <item>
      <title>Weekly Recon #3: AuthZ said deny. The parser said yes.</title>
      <link>https://defensive.works/recon/p/003</link>
      <guid isPermaLink="true">https://defensive.works/recon/p/003</guid>
      <pubDate>Tue, 05 May 2026 12:00:00 +0000</pubDate>
      <description>A one-megabyte padding trick that walks around Docker's last line of defense, the AWS session-policy pattern for forensic artifact collection, and the Kubernetes 1.36 features that quietly change who can impersonate whom.</description>
    </item>

    <item>
      <title>Weekly Recon #2: The identity acting is not the identity you think</title>
      <link>https://defensive.works/recon/p/002</link>
      <guid isPermaLink="true">https://defensive.works/recon/p/002</guid>
      <pubDate>Tue, 28 Apr 2026 12:00:00 +0000</pubDate>
      <description>A Claude Code skill riding authenticated Slack sessions, a Dependabot PR auto-merged 5 minutes after malicious publish, and the AWS pattern that scopes an MCP agent per tool call.</description>
    </item>

    <item>
      <title>Weekly Recon #1: The agent runs under its own AWS role, not yours</title>
      <link>https://defensive.works/recon/p/001</link>
      <guid isPermaLink="true">https://defensive.works/recon/p/001</guid>
      <pubDate>Tue, 21 Apr 2026 12:00:00 +0000</pubDate>
      <description>AWS Bedrock AgentCore, the IAM blast radius its starter toolkit quietly ships, and the 30-minute audit to run this week.</description>
    </item>

  </channel>
</rss>
