MemoryMapper – Map Both Native And Managed Assemblies Into Memory

[sc name=”ad_1″]

Memory Mapper is a lightweight library which allows the ability to map both native and managed assemblies into memory by either using process injection of a process specified by the user or self-injection; the technique of injecting an assembly into the currently running process attempting to do the injection. The library comes with tools not only to map assemblies, but with the capabilities to encrypt, decrypt, and generate various amounts of cryptographically strong data.

Requirements
Note: (For the running assembly using Memory Mapper ONLY — not for stubs/shellcode)

• Windows 7 SP1 & Higher
• .NET Framework 4.6.1

Features

• Explore the structure of a PE (portable executable)
• Read resources from both managed and native assemblies
• Map native assemblies into memory using process injection and self-injection
• Map managed assemblies into memory using process injection and other techniques
• Obtain an array of bytes for any file of any file size
• Encrypt and decrypt entire files and raw bytes
• Generate and validate checksums of files and raw bytes
• Generate cryptographically strong random data using a SecureRandom object
• Comes bundled with multiple encryption and hashing algorithmsEncryption
  • AES (ECB)
  • AES (CBC)
  • AES (CFB)
  • AES (OFB)
  • AES (CTR)

  Hashing

  • MD5
  • RIPEMD160
  • SHA1
  • SHA256
  • SHA384
  • SHA512

Examples

Native Injection
This example shows how to statically map a native assembly into memory using the NativeLoader tool. The example loads the file by reading all of its bytes from disk and then injects the PE (portable executable) associated with the bytes directly into memory. Using the native loader in conjunction with Dynamic Code Compilation found in my Amaterasu library one could accomplish on-the-fly code compilation and injection all from code in-memory.

using System;
using System.IO;
using System.Reflection;
using MemoryMapper;

namespace Example
{
class Program
{
static void Main(string[] args)
{
// Get the bytes of the file we want to load.
var filePath = "FileToReadBytesOf";
var fileBytes = File.ReadAllBytes(filePath);

bool isManaged = false;
try
{
// Note — this is one of the simplest variations of checking assemblies
var assemblyName = AssemblyName.GetAssemblyName(filePath);
if (assemblyName != null)
if (assemblyName.FullName != null)
isManaged = true;
}
catch { isManaged = false; }

if (!isManaged)
{
NativeLoader loader = new NativeLoader();
if (loader.LoadAssembly(fileBytes))
Console.WriteLine("Assembly loaded successfully!");
else
Console.WriteLine("Assembly could not be loaded.");
}

Console.Read();
}
}
}

Managed Injection
This example shows how to statically map a managed assembly into memory by reading in its bytes — or by using an embedded byte array — and then using the ManagedLoader to inject into a currently running process. Almost any managed assembly can be mapped using the provided ManagedLoader tool.

using System;
using System.IO;
using System.Reflection;
using MemoryMapper;

namespace Example
{
class Program
{
static void Main(string[] args)
{
// Get the bytes of the file we want to load.
var filePath = "FileToReadBytesOf";
var fileBytes = File.ReadAllBytes(filePath);

bool isManaged = false;
try
{
// Note — this is one of the simplest variations of checking assemblies
var assemblyName = AssemblyName.GetAssemblyName(filePath);
if (assemblyName != null)
if (assemblyName.FullName != null)
isManaged = true;
}
catch { isManaged = false; }

if (isManaged)
{
// Set the name of a surrogate process - the process we'll inject into.
var processName = "explorer.exe"; // Can also be the current process's name for self-injection.
ManagedLoader loader = new ManagedLoader();
if (loader.LoadAssembly(fileBytes, processName))
Console.WriteLine("Assembly loaded successfully!");
else
Console.WriteLine("Assembly could not be loaded.");
}

Console.Read();
}
}
}

Credits
Icon: DesignBolts
http://www.designbolts.com/

[sc name=”ad-in-article”]