!monitor (monitor read/write/execute to a range of memory)
Description of the '!monitor' command in HyperDbg.
Last updated
Description of the '!monitor' command in HyperDbg.
Last updated
!monitor
!monitor [Attribute (string)] [FromAddress (hex)] [ToAddress (hex)] [MemoryType (vapa)] [pid ProcessId (hex)] [core CoreId (hex)] [imm IsImmediate (yesno)] [sc EnableShortCircuiting (onoff)] [stage CallingStage (prepostall)] [buffer PreAllocatedBuffer (hex)] [script { Script (string) }] [asm condition { Condition (assembly/hex) }] [asm code { Code (assembly/hex) }] [output {OutputName (string)}]
!monitor [MemoryType (vapa)] [Attribute (string)] [FromAddress (hex)] [l Length (hex)] [MemoryType (vapa)] [pid ProcessId (hex)] [core CoreId (hex)] [imm IsImmediate (yesno)] [sc EnableShortCircuiting (onoff)] [stage CallingStage (prepostall)] [buffer PreAllocatedBuffer (hex)] [script { Script (string) }] [asm condition { Condition (assembly/hex) }] [asm code { Code (assembly/hex) }] [output {OutputName (string)}]
Monitors read or write or execute (or a combination of these operations) to a range of addresses. If any read or write or execute happens on the specified address range (memory), it will be triggered.
It is exactly like read/write/execute of Hardware Debug Registers but without any size and count limitation.
Please note that if you encounter an invalid address error when applying monitor hooks to a valid range, it is likely due to the page being paged-out or inaccessible in memory, often as a result of . This situation occurs because EPT hooks primarily work based on physical addresses, not virtual addresses. To resolve this issue, you can use the '' command. about tricks to make addresses available.
[Attribute (string)]
Can be one of these values (or a combination of these attributes like 'rw', 'rx', 'wx', 'rwx', etc.):
r: trigger in the case of reading.
w: trigger in the case of writing.
x: trigger in the case of executing.
[FromAddress (hex)]
The start virtual/physical address of where it needs to be monitored for reading or writing or executing (or a custom combination of these attributes). You have the option to utilize this parameter for either requesting the last address of the range or specifying the length (next parameter).
[l Length (hex)]
The start virtual/physical address of where it needs to be monitored for reading or writing or executing (or a custom combination of these attributes). You have the option to utilize this parameter for either requesting the length of monitoring memory or specifying the last address (previous parameter).
[ToAddress (hex)]
The end of the virtual/physical address of where it needs to be monitored for reading or writing or executing (or a custom combination of these attributes).
[MemoryType (vapa)] (optional)
Can be one of these values depending on whether the FromAddress and ToAddress are virtual addresses or physical addresses.
va: the address is a virtual address
pa: the address is a physical address
If you do not specify this event, it assumes that the address is a virtual address.
[pid ProcessId (hex)] (optional)
Optional value to trigger the event in just a specific process. Add pid xx to your command; thus, the command will be executed if the process id is equal to xx. If you don't specify this option, then by default, you receive events on all processes.
Still, in the case of user-mode debugging, HyperDbg will apply it only to the current active debugging process (not all the processes). In that case, you can specify pid all to intercept events from the entire system.
[core CoreId (hex)] (optional)
Optional value to trigger the event in just a specific core. Add core xx to your command thus command will be executed if core id is equal to xx. If you don't specify this option, then by default, you receive events on all cores.
[imm IsImmediate (yesno)] (optional)
Optional value in which yes means the results (printed texts in scripts) should be delivered immediately to the debugger. no means that the results can be accumulated and delivered as a couple of messages when the buffer is full; thus, it's substantially faster, but it's not real-time. By default, this value is set to yes.
[sc EnableShortCircuiting (onoff)] (optional)
[stage CallingStage (prepostall)] (optional)
[buffer PreAllocatedBuffer (hex)] (optional)
[script { Script (string) }] (optional)
[asm condition { Condition (assembly/hex) }] (optional)
[asm code { Code (assembly/hex) }] (optional)
[output {OutputName (string)}] (optional)
As the Context ($context pseudo-register in the event's script, r8 in custom code, and rdx in condition code register) to the event trigger, HyperDbg sends the virtual address (or physical address depending on the 'MemoryType' parameter) of the memory that has accessed and triggered this event.
It's a virtual address (or physical address depending on the 'MemoryType' parameter) equal to or between [from address] and [to address], so it's not a constant address and might differ in the range you entered.
When it comes to short-circuiting events, there are distinct behaviors for reads/writes and executions.
Short-circuiting for Reads/Writes: In this scenario, short-circuiting involves disregarding the execution of commands that read from or write to memory, such as MOV instructions. It is as if these instructions were never executed, and memory modifications are not performed.
Short-circuiting for Execution: Short-circuiting events for execution operate differently. It involves blocking the execution at the target address. For instance, if you wish to prevent execution on a specific page, you can achieve this by short-circuiting the event. Here is an example:
By adding event_sc(1);, HyperDbg is instructed to block execution, preventing any code within the target page from running.
If event_sc(1); is not used, HyperDbg will allow the target to execute normally for just one instruction before triggering again. The event will then be triggered for the next instruction, and so on. In essence, without event_sc(1);, it is like stepping through the instructions one by one, with each instruction in the target address range triggering the event. Conversely, specifying event_sc(1); will effectively block execution, preventing the target code on the target page from running.
For the Execute calling stage, the 'pre' calling stage is triggered prior to running the instruction that its execution leads to triggering the event, whereas the 'post' calling stage is triggered subsequent to running the target instruction. In addition, the 'all' calling stage will trigger the event in both cases.
This event supports three debugging mechanisms.
Break
Script
Custom Code
Imagine we want to put a monitor writes but not reads/executes on address from fffff800`4ed60000 to fffff800`4ed60100 , this will break to the debugger and gives the control back to us.
If we want reads but not writes/executes the memory with the length of 500 bytes.
If we want reads but not writes/executes.
If we want both reads and writes but not the executes.
Alternatively, we can use nt!Kd_DEFAULT_Mask too.
If we want to monitor any execution of instructions from this range, we can use the following command.
If we want to monitor any execution of instructions from the start address plus 0x7560 bytes, we can use the following command.
If we want to monitor any reads, writes, or executions of instructions from a PE section in the user-mode, we can use the following command.
If we want to monitor any reads, or writes, from a physical address, we can use the following command.
The above command is used when messages don't need to be delivered immediately.
Script (From File)
If you saved your script into a file, then you can add file: instead of a script and append the file path to it. For example, the following examples show how you can run a script from file:c:\users\sina\desktop\script.txt.
Run Custom Code (Unconditional)
Or if you want to use assembly codes directly, you can add an asm before the code.
Run Custom Code (Conditional)
Or if you want to use assembly codes directly, you can add an asm before the condition and also before the code.
Keep in mind that a conditional event can be used in Breaking to Debugger and Running Script too.
As EventType you can use one of the following events:
After that, you can send the start address (from address) of where you want to monitor in OptionalParam1and end address (to address) of where you want to monitor in OptionalParam2address DEBUGGER_GENERAL_EVENT_DETAIL. and OptionalParam3 can be either a virtual address or a physical address depending on the following enum:
Starting from v0.4, the support for execution interception or the 'x' attribute string is added to the HyperDbg debugger.
Starting from v0.9 the support for monitor physical memory is added to this command.
You shouldn't use any of !monitor, !epthook, and !epthook2 commands on the same page (4KB) simultaneously. For example, when you put a hidden hook (!epthook2) on 0x10000005, you shouldn't use any of !monitor or !epthook commands on the address starting from 0x10000000 to 0x10000fff.
You can use !epthook (just !epthook not !epthook2 and not !monitor) on two or more addresses on the same page (means that you can use the !epthook multiple times for addresses between a single page or putting multiple hidden breakpoints on a single page). But you can't use !monitor or !epthook2 twice on the same page.
Using the 'pid' parameter does not make sense if you specify a physical address as the 'MemoryType' and it is ignored.
Post-Nehalem Processor (EPT)
Optional value to ignore the emulation (skip execution) of the event. Add sc on to your command thus whenever the event is triggered, the effects and the execution of the actual event will be ignored. For more information, please read article. If you don't specify this option, then by default, all the events will be emulated (executed). By default, this value is set to off.
Optional value to configure the of the event. To trigger the event before the emulation, include stage pre in your command. Conversely, using stage post will cause the event to be triggered after the emulation. Additionally, using stage all will trigger the event both before and after the emulation. For more information, please read article. By default, this value is set to pre.
Optional value which reserves a safe to be accessed within the event codes.
A HyperDbg will be executed each time the event is triggered.
Optional assembly codes which check for in assembly.
Optional will be executed each time the event is triggered.
Optional output resource name for .
This event supports '', which means that you can configure HyperDbg to ignore its execution and its effects. For additional details, please refer to the article provided .
This event supports different . For the Read/Write calling stage, the 'pre' calling stage is triggered prior to the memory modification, whereas the 'post' calling stage is triggered subsequent to the memory modification. In addition, the 'all' calling stage will trigger the event in both cases. Using this mechanism you can see the memory before and after the modification (e.g., the MOV instruction modification).
You can the event in the 'pre' stage. For more information, please refer to the article provided .
Please read "" if you need a conditional event, a conditional event can be used in all "Break", "Script", and "Custom Code".
Using the following command, you can use HyperDbg's Script Engine. You should replace the string between braces (HyperDbg Script Here) with your script. You can find script examples .
You can use to forward the event monitoring results from this event and other events to an external source, e.g., File, NamedPipe, or TCP Socket. This way, you can use HyperDbg as a monitoring tool and gather your target system's behavior and use it later or analyze it on other systems.
Please read "" to get an idea about how to run a custom buffer code in HyperDbg.
Your custom code will be executed in vmx-root mode. Take a look at for more information. Running code in the VMX-root is considered "".
Monitoring reads and writes on an address range starting from fffff800`4ed60000 to fffff800`4ed60100 and run 3 nops whenever the event is triggered. Take a look at for more information.
Monitoring reads and executions on an address range starting from fffff800`4ed60000 to fffff800`4ed60100 and run 3 nops whenever the event condition is triggered and run 3 nops whenever the event is triggered. Take a look at and for more information.
This command uses the same method to .
Take a look at "" to see how it works.
If you need to reserve more pre-allocated pools for this command, you can use the '' command.
This command cannot be used simultaneously with the '' command.
If you want to monitor a large amount of memory, you have to consider tricks for . Please note that technically, you could use an unlimited amount of memory, but usually, in large memory ranges, there are page entries that are not available (paged out or never brought into memory by the OS). In those cases, you need to bring them into memory (force the OS to page them in) using the '' command. However, please consider that this command will inject a #PF (page fault) into the OS, and if the address is already valid, it disrupts OS semantics. The operating system does not expect to receive a page fault for a page that is already available, which might cause a triple fault and consequently a system restart or crash.
This command creates an . Starting from HyperDbg v0.7, events are guaranteed to keep the debuggee in a halt state (in the ); thus, nothing will change during its execution and the context (registers and memory) remain untouched. You can visit for more information.