<?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>InvisibleFerret on Melted in Hex</title>
    <link>https://meltedinhex.com/tags/invisibleferret/</link>
    <description>Recent content in InvisibleFerret on Melted in Hex</description>
    <image>
      <title>Melted in Hex</title>
      <url>https://meltedinhex.com/images/og-social.png</url>
      <link>https://meltedinhex.com/images/og-social.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:30:00 +0530</lastBuildDate>
    <atom:link href="https://meltedinhex.com/tags/invisibleferret/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dead Drops on the Blockchain: Reversing a DPRK npm Loader (PolinRider / A6-Shadow-15)</title>
      <link>https://meltedinhex.com/posts/polinrider-blockchain-dead-drop-npm/</link>
      <pubDate>Mon, 22 Jun 2026 00:30:00 +0530</pubDate>
      <guid>https://meltedinhex.com/posts/polinrider-blockchain-dead-drop-npm/</guid>
      <description>&lt;p&gt;We have all trained ourselves to look for the call home: the hard-coded IP, the suspicious &lt;code&gt;.xyz&lt;/code&gt; domain, the base64 URL that decodes to something hostile. This loader has none of that. Strip it to nothing and you find an address on the TRON blockchain, which points to a Binance Smart Chain transaction sent to a burn address so it can never be spent or deleted. The next stage sits in that transaction&amp;rsquo;s data field, XOR-encrypted. You cannot sinkhole it, and you cannot file a takedown against an immutable transaction replicated across thousands of nodes. The technique has a name, &lt;em&gt;EtherHiding&lt;/em&gt;, and it turns a public blockchain into bulletproof, censorship-proof storage for malware.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
