<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lab-Setup on 0xblack</title><link>https://0xblack.dev/tags/lab-setup/</link><description>Recent content in Lab-Setup on 0xblack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 01 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://0xblack.dev/tags/lab-setup/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up a Malware Analysis Lab on a Budget</title><link>https://0xblack.dev/notes/malware-lab-setup-on-a-budget/</link><pubDate>Sat, 01 Mar 2025 00:00:00 +0000</pubDate><guid>https://0xblack.dev/notes/malware-lab-setup-on-a-budget/</guid><description>&lt;p&gt;One of the first questions people ask when getting into malware analysis is: &lt;em&gt;how do I set up a safe environment to run samples without destroying my main machine?&lt;/em&gt; This is a fair concern — executing unknown binaries carelessly is how analysts end up with infected hosts.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s exactly what my setup looks like, how I built it cheaply, and the mistakes I made early on so you don&amp;rsquo;t have to.&lt;/p&gt;</description></item></channel></rss>