<?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>Security on MazaFard</title>
    <link>http://blog.fard.pt/tags/security/</link>
    <description>Recent content in Security on MazaFard</description>
    <image>
      <title>MazaFard</title>
      <url>http://blog.fard.pt/images/papermod-cover.png</url>
      <link>http://blog.fard.pt/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://blog.fard.pt/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Uncovering a Massive GitHub Supply Chain Attack: When a Friend&#39;s Repo Bites Back</title>
      <link>http://blog.fard.pt/posts/github-supply-chain-attack/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      <guid>http://blog.fard.pt/posts/github-supply-chain-attack/</guid>
      <description>&lt;p&gt;During a routine code review of a colleague&amp;rsquo;s GitHub repository, I identified an anomalous, highly obfuscated block of code embedded within a standard Python file. The use of randomized variable names and dense encoding strongly indicated malicious intent. Upon further investigation, this isolated finding revealed a sophisticated, large-scale supply chain attack currently affecting hundreds of repositories across GitHub.&lt;/p&gt;
&lt;p&gt;This article details the discovery, the reverse-engineering process, and actionable mitigation strategies to secure your development pipelines.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
