<?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 Pratik’s Localhost</title><link>https://pratikdabhi.in/tags/threat-hunting/</link><description>Recent content in Threat Hunting on Pratik’s Localhost</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>pratik.dabhi.4u@gmail.com (Pratik)</managingEditor><webMaster>pratik.dabhi.4u@gmail.com (Pratik)</webMaster><lastBuildDate>Sun, 08 Feb 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://pratikdabhi.in/tags/threat-hunting/index.xml" rel="self" type="application/rss+xml"/><item><title>From RSC to XMRig: Anatomy of a 28-Day Next.js Compromise</title><link>https://pratikdabhi.in/posts/rce-to-xmrig/</link><pubDate>Sun, 08 Feb 2026 12:00:00 +0000</pubDate><author>pratik.dabhi.4u@gmail.com (Pratik)</author><guid>https://pratikdabhi.in/posts/rce-to-xmrig/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 &lt;p&gt;What started as &amp;ldquo;why is CPU hot again?&amp;rdquo; ended with a full kill-chain reconstruction: public Next.js RSC RCE exploit, in-memory shell, persistent &lt;code&gt;toolers.cjs&lt;/code&gt; backdoor, then 28 days of Monero mining plus a dormant DDoS payload.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://pratikdabhi.in/posts/rce-to-xmrig/featured.png"/></item></channel></rss>