<?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>Projects on Deep Dives &amp; Weekend Projects</title><link>https://blog.lukasmay.com/projects/</link><description>Recent content in Projects on Deep Dives &amp; Weekend Projects</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Sun, 07 Dec 2025 22:25:58 -0500</lastBuildDate><atom:link href="https://blog.lukasmay.com/projects/index.xml" rel="self" type="application/rss+xml"/><item><title>LazyCargo</title><link>https://blog.lukasmay.com/projects/lazycargo/</link><pubDate>Sun, 07 Dec 2025 22:25:58 -0500</pubDate><guid>https://blog.lukasmay.com/projects/lazycargo/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;This is meant to be an outline of what I found while reversing the &lt;strong&gt;LazyCargo&lt;/strong&gt; malware sample. This malware sample is one part of the five pipedream/INCONTROLLER malware framework components discovered by several cybersecurity firms and government agencies. The LazyCargo malware is a Windows dropper for another module in the framework. I don&amp;rsquo;t have access to any of the other components, so I wrote a payload to run the LazyCargo malware at the end of the analysis to verify my findings from the static analysis.&lt;/p&gt;</description></item></channel></rss>