<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sandbox Evasion on Jordy van Raalte</title><link>https://jordyvanraalte.nl/tags/sandbox-evasion/</link><description>Recent content in Sandbox Evasion on Jordy van Raalte</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2026 14:52:22 +0200</lastBuildDate><atom:link href="https://jordyvanraalte.nl/tags/sandbox-evasion/index.xml" rel="self" type="application/rss+xml"/><item><title>Malware Obfuscation Part 3</title><link>https://jordyvanraalte.nl/posts/malware-obfuscation-part-3/</link><pubDate>Sun, 12 Jul 2026 14:52:22 +0200</pubDate><guid>https://jordyvanraalte.nl/posts/malware-obfuscation-part-3/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;In this post I explore several sandbox evasion techniques for malware. It’s part of my ongoing Malware Development series where I discover the world of malware development.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;⚠️ &lt;strong&gt;Warning:&lt;/strong&gt; This content is for educational and defensive security research purposes only. Do not use these techniques on systems or networks you do not own or have explicit permission to test.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1 id="sandbox-evasion"&gt;Sandbox evasion&lt;/h1&gt;
&lt;p&gt;Previously, we implemented function obfuscation into the malware. Function obfuscation only protects against static analysis. Once the sample runs in a sandbox, a malware analyst can observe its real behavior and reverse engineer it. Sandbox evasion is one of the countermeasures for malware analysists. There are many ways for sandbox evasion. In the blog, we will be focusing on the following sandbox evasion techniques:&lt;/p&gt;</description></item></channel></rss>