Sophos X-Ops<p>What's up with that <a href="https://infosec.exchange/tags/GuLoader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GuLoader</span></a> URL?</p><p>The command uses a URL format that looks like a hexadecimal value, a dot, and then a decimal number.</p><p>It turns out that this is a variation of the so-called <a href="https://infosec.exchange/tags/dotless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotless</span></a> IP address format. </p><p>Back in 1999, there was a vulnerability in Internet Explorer where someone figured out this very odd bug. CVE-1999-1087 (<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-1087" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cve.mitre.org/cgi-bin/cvename.</span><span class="invisible">cgi?name=CVE-1999-1087</span></a>) describes this bug and the strange formatting of the URL. </p><p>Back then, <span class="h-card"><a href="https://infosec.exchange/@threatresearch" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>threatresearch</span></a></span> created a little Excel spreadsheet that shows how to do this conversion. In essence, a dotless IP address is the decimal representation of a hexadecimal representation of the four octets in an IPv4 address.</p><p>The spreadsheet tells the story better than I can with words, so take a look at this screenshot of it, with the update to show how the <a href="https://infosec.exchange/tags/GuLoader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GuLoader</span></a> threat actors have adopted this method. Basically they use the hexadecimal value for the first of the four IPv4 octets, and then the decimal conversion value for the final three octets of the IPv4 address. It's very clever, because there still isn't a very strong understanding of this low-level way that network stacks interpret IPv4 addresses. Apparently PowerShell does interpret it correctly.</p><p>Just another weirdness and we haven't even gotten to the malware, itself.</p><p><a href="https://infosec.exchange/tags/GuLoader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GuLoader</span></a> <a href="https://infosec.exchange/tags/Remcos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Remcos</span></a> <a href="https://infosec.exchange/tags/maltax" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>maltax</span></a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/dotlessIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotlessIP</span></a> <a href="https://infosec.exchange/tags/retroCVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>retroCVE</span></a></p><p>6/</p>