<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory Forensics on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/memory-forensics/</link>
    <description>Recent content in Memory Forensics on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 06 Sep 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/memory-forensics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Identification of (malicious) modifications in memory-mapped image files</title>
      <link>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</link>
      <pubDate>Wed, 06 Sep 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</guid>
      <description>&lt;p&gt;I’m happy to announce the publication of the paper&#xA;&lt;a href=&#34;https://dfrws.org/wp-content/uploads/2023/07/block-windowsmemoryforensics.pdf&#34;&gt;Windows memory forensics: Identification of (malicious) modifications in memory-mapped image files&lt;/a&gt;&#xA;at this years DFRWS USA, and the release of the corresponding&#xA;&lt;a href=&#34;https://github.com/f-block/volatility-plugins#imgmalfind&#34;&gt;volatility plugin&lt;/a&gt;.&#xA;With this research came also an update to the Ptenum family (affecting&#xA;especially the &lt;code&gt;ptemalfind&lt;/code&gt; plugin), which makes the plugins reliable in&#xA;identifying modified pages despite memory combining, so make sure to grab the&#xA;newest version from the Github repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some experiments with Process Hollowing</title>
      <link>https://insinuator.net/2022/09/some-experiments-with-process-hollowing/</link>
      <pubDate>Thu, 29 Sep 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/09/some-experiments-with-process-hollowing/</guid>
      <description>&lt;p&gt;Process Hollowing is a technique used by various malware families (such as&#xA;FormBook, TrickBot and Agent Tesla) to hide their malicious code within a benign&#xA;appearing process. The typical workflow for setting up such a&#xA;&lt;a href=&#34;https://attack.mitre.org/techniques/T1055/012/&#34;&gt;hollowed process&lt;/a&gt; is as&#xA;follows:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Create a new process (victim) using a benign executable, in suspended state.&lt;/li&gt;&#xA;&lt;li&gt;Unmap the executable from that process.&lt;/li&gt;&#xA;&lt;li&gt;Allocate memory for the malicious executable at the address of the&#xA;previously mapped victim executable.&lt;/li&gt;&#xA;&lt;li&gt;Write the malicious executable to the new memory area and potentially apply&#xA;relocations.&lt;/li&gt;&#xA;&lt;li&gt;Adjust the entry point.&lt;/li&gt;&#xA;&lt;li&gt;Resume process.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;We will refer to this as the “normal” Process Hollowing workflow. There are also&#xA;variants of this technique, one being to not unmap the original executable and&#xA;to allocate the new memory somewhere else. We will call this one no-unmap. But&#xA;wait, why does malware not simply overwrite the existing executable but creates&#xA;a new memory area which stands out due to its characteristics? In this blog post&#xA;we will have a closer look at this overwrite approach but also on the no-unmap&#xA;method, their effects on analysis/detection tools and on some tricks to make the&#xA;detection harder. We are also releasing Proof of Concept implementations of all&#xA;mentioned tools/plugins (the links are at the end of this post).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of PTE Analysis plugins for Volatility 3</title>
      <link>https://insinuator.net/2021/12/release-of-pte-analysis-plugins-for-volatility-3/</link>
      <pubDate>Fri, 31 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/12/release-of-pte-analysis-plugins-for-volatility-3/</guid>
      <description>&lt;p&gt;I’m happy to announce the&#xA;&lt;a href=&#34;https://github.com/f-block/volatility-plugins&#34;&gt;release&lt;/a&gt; of several plugins for&#xA;Volatility 3 that allow you to dig deeper into the memory analysis. One of those&#xA;plugins is &lt;code&gt;PteMalfind&lt;/code&gt;, which is essentially an improved version of &lt;code&gt;malfind&lt;/code&gt;.&#xA;Another one is &lt;code&gt;PteResolve&lt;/code&gt; which, similarly to the WinDBG command &lt;code&gt;!pte&lt;/code&gt;,&#xA;allows you to inspect Page Table Entry (PTE) information for e.g., a given&#xA;virtual address. In this blog post we will have a closer look at these and more&#xA;plugins, and the &lt;code&gt;PteEnumerator&lt;/code&gt; base class and what you can do with it. The&#xA;memory dump used for this blog post is available&#xA;&lt;a href=&#34;https://ernw.de/download/blogposts/pte_analysis/mem.dump.zip&#34;&gt;here&lt;/a&gt;. Some of&#xA;the injection tools used in this blog post can be gathered from&#xA;&lt;a href=&#34;https://github.com/f-block/DFRWS-USA-2019/tree/master/tools&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
