<?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>Threat Intelligence on howtoit</title><link>https://howtoit.org/tags/threat-intelligence/</link><description>Recent content in Threat Intelligence on howtoit</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://howtoit.org/tags/threat-intelligence/index.xml" rel="self" type="application/rss+xml"/><item><title>TeamPCP published their own malware on GitHub — with an instruction manual</title><link>https://howtoit.org/posts/shai-hulud-open-source/</link><pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/shai-hulud-open-source/</guid><description>On May 12, TeamPCP posted the full source code for the Shai-Hulud worm to GitHub under the MIT license. Copycat actors were forking it within hours. Here&amp;#39;s what happened and what it means.</description></item><item><title>How a poisoned VS Code extension breached GitHub — and the npm attack that started it all</title><link>https://howtoit.org/posts/teampcp-supply-chain-attack/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/teampcp-supply-chain-attack/</guid><description>A breakdown of the TeamPCP supply chain campaign — from the TanStack npm compromise to the Nx VSCode extension that breached 3,800 GitHub internal repositories.</description></item></channel></rss>