Skip to content

Moneta

What Moneta does

Using this tool

Moneta supports memory analysis. In this guide, you will use it to review a controlled process for suspicious memory characteristics and validate the result. Follow the steps below and keep the output with your notes.

Tool guide at a glance

Investigation task

Review a controlled process for suspicious memory characteristics and validate the result.

Starting material

An authorised running Windows training VM and the current PID of a process to inspect.

What to record

A saved live process scan with the PID, scan time, command and findings checked against known process behaviour.

Evidence and safety

Moneta scans live processes rather than an acquired memory image file. Record the effect of running it and validate possible false positives. Record the input identifier, tool version, relevant commands or settings, time and time zone, output location, and any errors or limitations as you work.

Choose your journey

How the labs complement this guide

The Interactive Lab uses example records to practise investigation decisions. It does not run the installed tool or establish how that version behaves. The Full Lab uses your own training environment and evidence. Obtain or create the required input before starting; a case name in an exercise is not a download.

Accessing Moneta in SUSA

Moneta is a free, open source live memory analysis tool for Windows. It scans the memory of running processes and looks for indicators of compromise (IOCs) that are commonly associated with malware, process injection, shellcode, reflective DLL loading, process hollowing, and other fileless attack techniques.

Download Moneta from the GitHub repository.

Move the executable to C:\Tools\Moneta.

Open an administrator Command Prompt and navigate to C:\Tools\Moneta. List the running processes:

tasklist

Replace the example process identifier with the current PID of the authorised process you want to inspect, then run:

Moneta64.exe -m ioc -p 1188

Moneta findings require analyst validation, as legitimate software may generate false positives. Prioritise investigation of unbacked executable memory, private RWX regions, injected code, reflectively loaded DLLs, and suspicious memory artefacts in high risk processes.