<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ide-Security on Mazin Ahmed</title><link>https://mazinahmed.net/tags/ide-security/</link><description>Recent content in Ide-Security on Mazin Ahmed</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mazinahmed.net/tags/ide-security/index.xml" rel="self" type="application/rss+xml"/><item><title>The GitHub Breach Through VS Code Is the One I Warned About</title><link>https://mazinahmed.net/blog/github-vscode-breach/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/github-vscode-breach/</guid><description>&lt;p&gt;&#10;&#10;&#10;&#10;&#10;&#10;&#10; &#10; &#10;&lt;figure&gt;&lt;img src="https://raw.githubusercontent.com/mazen160/public/master/static/images/334d545c-6cef-4b93-b986-cb07927a47f1-compressed.png" alt="" class="mx-auto my-0 rounded-md" /&gt;&#10;&lt;/figure&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;If you haven&amp;rsquo;t heard the news, GitHub confirmed unauthorized access to internal repositories through a malicious VS Code extension. I&amp;rsquo;ve been warning about this. I predicted it would happen in my talk &lt;a href="https://mazinahmed.net/blog/publishing-malicious-vscode-extensions/" target="_blank" rel="noreferrer"&gt;Compromising Developers with Malicious Extensions&lt;/a&gt; last December at Black Hat MEA, where I presented several flaws in VS Code and the marketplace and how people can use them to run supply chain attacks.&lt;/p&gt;&#10;&lt;p&gt;We still don&amp;rsquo;t have the full details yet, but here&amp;rsquo;s how I see it.&lt;/p&gt;</description></item></channel></rss>