<?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-Security on krash.dev</title><link>https://krash.dev/tags/supply-chain-security/</link><description>Recent content in Supply-Chain-Security on krash.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 08:29:09 +0530</lastBuildDate><atom:link href="https://krash.dev/tags/supply-chain-security/rss.xml" rel="self" type="application/rss+xml"/><item><title>Before Your Code Runs: Node.js</title><link>https://krash.dev/posts/before-your-code-runs/nodejs/</link><pubDate>Sun, 29 Mar 2026 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/before-your-code-runs/nodejs/</guid><description>&lt;blockquote&gt;&lt;p&gt;This post is part of the &lt;strong&gt;&lt;a href="https://krash.dev/before-your-code-runs/"&gt;Before Your Code Runs&lt;/a&gt;
&lt;/strong&gt; series, cataloguing the hidden, implicit code execution surfaces in programming language runtimes and toolchains.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;Node.js and npm sit underneath a huge chunk of the modern web. It&amp;rsquo;s the runtime that made JavaScript a &amp;ldquo;real&amp;rdquo; backend language, and npm is the largest package registry in the world. That&amp;rsquo;s a lot of trust in a lot of code.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s roughly what happens when Node starts:&lt;/p&gt;</description></item><item><title>Before Your Code Runs: Python</title><link>https://krash.dev/posts/before-your-code-runs/python/</link><pubDate>Sun, 29 Mar 2026 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/before-your-code-runs/python/</guid><description>&lt;blockquote&gt;&lt;p&gt;This post is part of the &lt;strong&gt;&lt;a href="https://krash.dev/before-your-code-runs/"&gt;Before Your Code Runs&lt;/a&gt;
&lt;/strong&gt; series, cataloguing the hidden, implicit code execution surfaces in programming language runtimes and toolchains.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;Python is probably the most beloved language in the world right now. It&amp;rsquo;s everywhere: data science, web backends, DevOps glue, AI/ML pipelines, you name it. And because it&amp;rsquo;s everywhere, attackers love it too. The thing is, most Python developers think execution starts when you type &lt;code&gt;python app.py&lt;/code&gt;. It doesn&amp;rsquo;t. Not even close.&lt;/p&gt;</description></item><item><title>Reputation Farming in OSS: A Threat to Building Trust</title><link>https://krash.dev/posts/reputation-farming/</link><pubDate>Thu, 27 Jun 2024 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/reputation-farming/</guid><description>&lt;p&gt;This issue complicates the open source and supply chain security space. For attacks like xz, such strategies can be used by attackers to build &amp;ldquo;fake&amp;rdquo; trust among fellow OSS community members.&lt;/p&gt;
&lt;p&gt;A few days ago, &lt;a href="https://openssf.slack.com/archives/C019M98JSHK/p1719225074824219" target="_blank" rel="noopener noreferrer"&gt;this discussion ignited in the OSSF Slack&lt;/a&gt;, which talked about the issue of credibility farming in several open source repositories.&lt;/p&gt;
&lt;img loading="lazy" decoding="async" src="../images/slack-message.png" alt="OSSF Slack Discussion"&gt;&lt;p&gt;So, the issue revolves around GitHub (or equivalent platforms) accounts approving or commenting on old pull requests and issues that were already resolved or closed, where these meaningless contributions show up prominently on the user&amp;rsquo;s profile and activity feed, making their involvement seem more significant than it actually is, without closer look.&lt;/p&gt;</description></item><item><title>Two Bits on the xz Vulnerability</title><link>https://krash.dev/posts/xz-vulnerability/</link><pubDate>Mon, 01 Apr 2024 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/xz-vulnerability/</guid><description>&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;GitHub Repository&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/tukaani-project/xz/releases/tag/v5.6.0" target="_blank" rel="noopener noreferrer"&gt;xz (Suspended)&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Source Code&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://git.tukaani.org/?p=xz.git" target="_blank" rel="noopener noreferrer"&gt;https://git.tukaani.org/?p=xz.git&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Threat Actor&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/JiaT75" target="_blank" rel="noopener noreferrer"&gt;Jia Tan (GitHub)&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;CVE Number&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-3094" target="_blank" rel="noopener noreferrer"&gt;CVE-2024-3094 (CVSS 10.0)&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Vulnerability Type&lt;/td&gt;
 &lt;td&gt;Remote Code Execution&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Attack Category&lt;/td&gt;
 &lt;td&gt;Social Engineering, Supply Chain Attack&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h1 id="what-does-xz-module-do"&gt;What does &lt;code&gt;xz&lt;/code&gt; module do?&lt;a class="heading-anchor" href="#what-does-xz-module-do" aria-label="Link to this section"&gt;#&lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;XZ Utils is a set of free and open-source data compression utilities that provide high compression ratios and fast decompression. It primarily uses the &lt;a href="https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Markov_chain_algorithm" target="_blank" rel="noopener noreferrer"&gt;LZMA compression algorithm&lt;/a&gt;
, which is an algorithm for lossless data compression.&lt;/p&gt;</description></item><item><title>Handling Deprecated Dependencies In Your Project</title><link>https://krash.dev/posts/handling-deprecated-dependencies/</link><pubDate>Tue, 07 Nov 2023 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/handling-deprecated-dependencies/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: Just a heads up, while we&amp;rsquo;re diving into ways to tackle the problem of dependency depreciation, there&amp;rsquo;s no one-size-fits-all solution here. It&amp;rsquo;s a bit of a wild ride dealing with supply chain security and those pesky deprecated dependencies, so don&amp;rsquo;t expect a quick fix!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The issue of using deprecated dependencies has persisted for quite some time, and it&amp;rsquo;s gaining increased attention. Many projects continue to incorporate deprecated dependencies.&lt;/p&gt;
&lt;p&gt;I was inspired to write this blog after coming across &lt;a href="https://www.linkedin.com/posts/rorym_softwaresupplychainsecurity-activity-7127600960364797954-rAJE/" target="_blank" rel="noopener noreferrer"&gt;a LinkedIn post by Rory McCune&lt;/a&gt; and several other posts over the past few weeks.&lt;/p&gt;</description></item><item><title>VS Code Security: Looking at the IDE from Security Lens</title><link>https://krash.dev/posts/attacking-vs-code/</link><pubDate>Thu, 14 Sep 2023 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/attacking-vs-code/</guid><description>&lt;p&gt;While perusing &lt;a href="https://survey.stackoverflow.co/2023/#section-most-popular-technologies-integrated-development-environment" target="_blank" rel="noopener noreferrer"&gt;StackOverflow&amp;#39;s 2023 Developer Survey&lt;/a&gt; (yes, we developers have our own version of celebrity gossip), I couldn&amp;rsquo;t help but notice that our trusty VSCode is still riding high as the undisputed IDE champ. With a whopping 73% of the developer vote, it&amp;rsquo;s safe to say that VSCode has firmly planted its flag. But, like any superstar, it&amp;rsquo;s not immune to the spotlight&amp;rsquo;s glare, especially when it comes to security. And in this blog, we&amp;rsquo;ll explore the security aspects that every VSCode user should consider.&lt;/p&gt;</description></item></channel></rss>