<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container Orchestration on Cliff Hults</title><link>https://www.haguest.com/tags/container-orchestration/</link><description>Recent content in Container Orchestration on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/container-orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>Supply Chain Attacks Start in Your Build Cache</title><link>https://www.haguest.com/posts/2026-04-11-axios-supply-chain/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-04-11-axios-supply-chain/</guid><description>&lt;p>On March 25, 2025, a malicious version of the axios npm package (version 1.14.1) was published to the npm registry. It contained a bundled dependency called &lt;code>plain-crypto-js@4.2.0&lt;/code>, which was later confirmed to be malicious. The package was identified and removed from the npm registry within roughly three hours.&lt;/p>
&lt;p>For most organizations, three hours sounds manageable. For us, it wasn&amp;rsquo;t that simple.&lt;/p></description></item></channel></rss>