So for example if say someone tries to change a byte or tries to dump or inspect the file in memory and ITS detected.
Is there a way to fully kill the file for example
if EP_CheckupIsProtected = false
if EP_CheckupVirtualizationTools = false
or Inline Patching or something is TRIGGERD
But upon FIRST execution it would capture the users HWID and other details.
then if any are trigger it would kill the code or it would trigger say something in RISC VM to be like OK then just 000000 the entire code make it dead
Then we could send that data to a server so if they try to executre again its blocked and the same thing was to happen aka a "fail safe"
Can you explain if this already exists. As I did try and change a byte and put the byte back and the file ran fine
But if someone is doing that they are not trying to change a "Single" byte they are probably reversing or inspecting the file ! etc etc etcmy use age is the .dll loads into an application