<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>threat-hunting on Raúl Pastor</title><link>https://pixelotes.com/tags/threat-hunting/</link><description>Recent content in threat-hunting on Raúl Pastor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pixelotes.com/tags/threat-hunting/index.xml" rel="self" type="application/rss+xml"/><item><title>Supply Chain Security: The Forgotten Front</title><link>https://pixelotes.com/blog/supply-chain-security/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://pixelotes.com/blog/supply-chain-security/</guid><description>&lt;p&gt;Most teams have a patching process for servers and laptops. Far fewer have one for the code they did not write: npm packages, Python libraries, container base images, IDE extensions. We add a dependency once, it works, and nobody looks at it again.&lt;/p&gt;&#10;&lt;p&gt;That is the gap attackers are using. You do not need to breach a company if you can get your code into something the company already trusts and installs automatically.&lt;/p&gt;</description></item></channel></rss>