<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Blogs on ThreatCat.ch Blog</title>
		<link>https://www.threatcat.ch/blog/</link>
		<description>Recent content in Blogs on ThreatCat.ch Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.threatcat.ch/blog/feed.xml" rel="self" type="application/atom+xml" />
			<item>
				<title>Unpacking a Multi-Stage Loader: From Embedded Payloads to Cobalt Strike Beacon</title>
				<link>https://www.threatcat.ch/blog/unpacking-a-multi-stage-loader/</link>
				<pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/unpacking-a-multi-stage-loader/</guid>
				<description>&lt;p&gt;During routine monitoring, Threatcat’s anomaly detection identified an interesting file hosted on SwissTransfer at the end of July 2026. The file was flagged as anomalous and subsequently investigated in more detail. The associated URLScan result is available &lt;a href=&#34;https://urlscan.io/result/019fa31a-dc32-759a-9b02-d37ac6b216a4/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Encryption as Obfuscation</title>
				<link>https://www.threatcat.ch/blog/encryption-as-obfuscation/</link>
				<pubDate>Thu, 07 Dec 2023 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/encryption-as-obfuscation/</guid>
				<description>&lt;p&gt;Some time ago, we analyzed a sample with an encrypted payload using an interesting technique. Unfortunately, we can&amp;rsquo;t share the sample, and it isn&amp;rsquo;t available on Virustotal neither. In order to show this technique - and its weakness - we decided to write a simple program ourselves implementing something similar, though not identical. This test sample is available &lt;a href=&#34;assets/sample.bin&#34;&gt;here&lt;/a&gt; - and we promise it does not contain any malicious code. If you run it, you&amp;rsquo;ll notice it doesn&amp;rsquo;t do anything. Under the right circumstances, it should decrypt an embedded payload and write it to a file &lt;code&gt;output.dat&lt;/code&gt;. And of course, we&amp;rsquo;d like to find this decrypted data.&lt;/p&gt;</description>
			</item>
			<item>
				<title>When hunters become prey - CSTI (?) in Nuclei</title>
				<link>https://www.threatcat.ch/blog/when-hunters-become-prey/</link>
				<pubDate>Thu, 29 Jun 2023 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/when-hunters-become-prey/</guid>
				<description>&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;We discovered what we believe is a &lt;a href=&#34;https://portswigger.net/kb/issues/00200308_client-side-template-injection&#34;&gt;Client Side Template Injection (CSTI)&lt;/a&gt; vulnerability in &lt;a href=&#34;https://github.com/projectdiscovery/nuclei&#34;&gt;Nuclei&lt;/a&gt; that allows an attacker to crash the scanner (Denial of Service - DoS) and, under certain circumstances, even leak secret keys. We choose the wording &lt;em&gt;&amp;ldquo;we believe&amp;rdquo;&lt;/em&gt; here, because ProjectDiscovery denies that it is a security issue and that it works as intended. Our proof-of-concept codes (PoCs) demonstrate these scenarios and how to find plugins vulnerable to at least the DoS by crashing the scanner.&lt;/p&gt;</description>
			</item>
			<item>
				<title>FENtastic chessadecimal encryPGN: Solution</title>
				<link>https://www.threatcat.ch/blog/fentastic-chessadecimal-encrypgn-solution/</link>
				<pubDate>Thu, 27 Apr 2023 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/fentastic-chessadecimal-encrypgn-solution/</guid>
				<description>&lt;p&gt;This blog post shows different ways to solve the &lt;a href=&#34;https://www.threatcat.ch/blog/fentastic-chessadecimal-encrypgn/&#34;&gt;Capture the Flag (CTF) challenge&lt;/a&gt; posted on April 21, 2023.&lt;/p&gt;</description>
			</item>
			<item>
				<title>FENtastic chessadecimal encryPGN</title>
				<link>https://www.threatcat.ch/blog/fentastic-chessadecimal-encrypgn/</link>
				<pubDate>Fri, 21 Apr 2023 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/fentastic-chessadecimal-encrypgn/</guid>
				<description>&lt;figure&gt;&#xA;&#x9;&#x9;&lt;img src=&#34;assets/threatcat-on-chessboard.jpg&#34; alt=&#34;ThreatCat on chessboard&#34;&gt;&#xA;&#x9;&#x9;&lt;figcaption&gt;ThreatCat on chessboard&lt;/figcaption&gt;&#xA;&#x9;&lt;/figure&gt;&lt;p&gt;We created a CTF to celebrate the World Chess Championship 2023 between  Ian Nepomniachtchi and Ding Liren:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Undo .NET Constant Obfuscation in IDA Pro</title>
				<link>https://www.threatcat.ch/blog/undo-dotnet-constant-obfuscation-in-ida-pro/</link>
				<pubDate>Thu, 09 Mar 2023 00:00:00 +0000</pubDate>
				<guid>https://www.threatcat.ch/blog/undo-dotnet-constant-obfuscation-in-ida-pro/</guid>
				<description>&lt;p&gt;While .NET malware samples are usually easy to decompile using dnspy and similar tools, possibly after an initial unpacking step using dnspy&amp;rsquo;s debugger or a dedicated unpacker like ConfuserEx, there often remain additional &amp;ldquo;small&amp;rdquo; obfuscations of strings or constants. While these can be reverted manually, this often results in a tedious process, which calls for automation. IDA Pro,  the traditional tool to perform such tasks in x86 binaries, offers a great Python interface - unfortunately only in its commercial version. Until some time ago, the support for .NETs intermediate language MSIL (Microsoft Intermediate Language) was limited, in particular when binary patching was required, but current versions can deal with this. We&amp;rsquo;ll look into a very simple example of a constant obfuscation we sometimes saw, and how a simple script can do the job. While the example is a real one, it&amp;rsquo;s nearly trivial and could also solved in other ways; but we think it&amp;rsquo;s a nice educational study.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
