You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see below, some functions appear in plain text inside the binary :
to hide this, here's a technique (example in cpp ):
// sVirtualAllocEx = xor of string "VirtualAlloc" with key (outside of the packer)unsignedcharsVirtualAllocEx[] = { 0x3b, 0x10, 0x1, 0x11, 0x16, 0xa, 0x6, 0x28, 0x1};
// xor second time to obtain the plain text string XOR((char *) sVirtualAllocEx, sizeof(sVirtualAllocEx), key, sizeof(key));
// call the fonction
pVirtualAllocEx = GetProcAddress(GetModuleHandle("kernel32.dll"), sVirtualAllocEx);
in the end, we add an abstraction layer, so that if we run the "strings" command again, we won't see our function appear.
The text was updated successfully, but these errors were encountered:
As you can see below, some functions appear in plain text inside the binary :
to hide this, here's a technique (example in cpp ):
in the end, we add an abstraction layer, so that if we run the "strings" command again, we won't see our function appear.
The text was updated successfully, but these errors were encountered: