<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident on Catalyst9 Engineering</title><link>https://blog.catalyst9.ai/tags/incident/</link><description>Recent content in Incident on Catalyst9 Engineering</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 -0600</lastBuildDate><atom:link href="https://blog.catalyst9.ai/tags/incident/index.xml" rel="self" type="application/rss+xml"/><item><title>The GitHub VS Code Extension Breach, in Threat-Model Terms</title><link>https://blog.catalyst9.ai/posts/2026-05-20-github-vscode-extension-breach/</link><pubDate>Wed, 20 May 2026 00:00:00 -0600</pubDate><guid>https://blog.catalyst9.ai/posts/2026-05-20-github-vscode-extension-breach/</guid><description>GitHub&amp;rsquo;s internal repos got exfiltrated through a poisoned VS Code extension. Here&amp;rsquo;s the threat model that actually matters — and what credential-storage architecture can and can&amp;rsquo;t do about it.</description></item></channel></rss>