<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Supply Chain - Hugo FixIt Blog</title><link>https://pullsec.io/incident/supply-chain/</link><description>This is my new Hugo FixIt site</description><generator>Hugo 0.164.0 &amp; FixIt v1.0.0-alpha-mtcmp1fx</generator><language>en</language><lastBuildDate>Tue, 05 May 2026 15:10:00 +0200</lastBuildDate><atom:link href="https://pullsec.io/incident/supply-chain/index.xml" rel="self" type="application/rss+xml"/><item><title>Xinference PyPI Supply Chain Attack</title><link>https://pullsec.io/incident/supply-chain/xinference/</link><pubDate>Mon, 04 May 2026 08:23:14 +0200</pubDate><guid>https://pullsec.io/incident/supply-chain/xinference/</guid><category domain="https://pullsec.io/categories/incident/">Incident</category><description>&lt;p&gt;In my previous posts, I focused on kernel vulnerabilities and exploitation primitives such as use-after-free, page cache corruption, and metadata confusion.&lt;/p&gt;
&lt;p&gt;This case is different, is not a vulnerability in code is a compromise of trust.&lt;/p&gt;</description></item></channel></rss>