Comment on page
Variables & Assignments
Description of variables and assignments
By using a simple lvalue register assignment, the user is able to change the value of registers.
syntax
@register = expression;
Example 1
@rax = 0x55;
Example 2
@r15 = poi(@rcx);
Example 3
if ( @rcx == 0x55) {
@rcx = @rdx + @rax + 12;
}
In HyperDbg's script engine, all the variables are defined without Type, and all of them are considered unsigned 64-bit integers. You can save results of functions and boolean expressions or results of mathematical calculations alongside 64-bit addresses to the variables.
The variables can be used as an input to other functions or might be used in conditional statements or loops.
If you want to assign a symbol name (e.g., address of a Windows function or a Windows global variable) to a script engine variable, you should specify the module name along with a bang '!' character; otherwise, it's interpreted as a variable name. For example,
x = ExAllocatePoolWithTag; is equal to assigning the a script engine variable named ExAllocatePoolWithTag to a variable named x. However, x = nt!ExAllocatePoolWithTag; means assigning the function address from the nt module to the x variable.The following example shows the assigning
0 to a variable named my_variable.my_variable = 0;
You can also assign registers or pseudo-registers to the variables.
my_variable = $proc + 0x10;
my_variable = @rax - @rcx + 8;
Also, you can assign the results of functions to the variables.
my_variable = check_address(@rcx);
Or, you can decrement or increment variables by one.
my_variable++; // equals to my_variable = my_variable + 1;
my_variable--; // equals to my_variable = my_variable - 1;
Local variables won't be changed in the case of a core's context, which means you can save the variable and expect to reread it next time you access the variable from the same core. But of course, the local variables are not available in other cores.
Like local variables, all global variables are defined without type, and all of them are considered unsigned 64-bit integers.
The variables can be used as an input to other functions or might be used in conditional statements or loops.
The difference between local variables and global variables is that the global variables start with a
. DOT.The following example shows the assigning
0 to a global variable named .my_variable..my_variable = 0;
You can also assign registers or pseudo-registers to the global variables.
.my_variable = $proc + 0x10;
.my_variable = @rax - @rcx + 8;
Also, you can assign the results of functions to the global variables.
.my_variable = check_address(@rcx);
Or, you can decrement or increment variables by one.
.my_variable++; // equals to my_variable = my_variable + 1;
.my_variable--; // equals to my_variable = my_variable - 1;
You should not write to a global variable simultaneously from different cores. It's clear that other cores might trigger the same event and use the global variable or modify that variable.
To solve this problem, you can use spinlock functions. If you want to perform mathematical calculations on different global variables, you should use interlocked functions instead of performing them using regular math operators.
//
// First, we should create a separate global variable as the lock
//
spinlock_lock(.my_global_variable_lock);
//
// Now, it's safe to change the global variable in a multi-core
// environment
//
.my_global_var = 0x1234;
//
// At last, we should release the lock
//
spinlock_unlock(.my_global_variable_lock);
As another example, assume that we want to count the number of times a function is called. For this purpose, we need a global variable to hold this number. You can safely use interlocked_increment for this purpose, and for other mathematical operations or atomic exchange operations, you can use other interlocked functions.
interlocked_increment(.my_global_counter);
If you are running HyperDbg on a single-core machine, there is no need to use a spinlock or use interlocked functions for calculations; you can directly modify them without any problem.
Both global variables and local variables are initialized with
NULL.eb modifies a single byte.ed modifies a dwrod.eq modifies a qword value.The following code edits memory (quad-word) at
fffff8031d44fde0 and change it to 0x12345678deadbeef.IsEditApplied = eq(fffff8031d44fde0, 0x12345678deadbeef);
The following code changes a byte to 0x90 at the location that the @rcx register is pointing to, then adds 0x8 to it.
IsEditApplied = eb(poi(@rcx)+8, 0x90);
Last modified 1yr ago