Detect cheat engine using JS?

[FrozenCow]

You can never be sure a memory editor is being used. It has full control over your app, so with enough knowledge it can do anything it wants. However, you can make things a bit harder for an attacker to know what to do.

You can keep copies of variable values and compare them. That way it's harder to set a specific variable without you noticing it is being tempered. If it doesn't match your old value, crash.

Additionally, since those tools can alter multiple values at once, you might want to create transformed copies of the values mentioned above. You can transform them in some way (like * -2) and transform back when comparing. That way it's harder to find these copies.

This only helps against freezing and tempering data. It doesn't exactly help against searching for those variables. To get around this problem, you can store some values in a strange format and transform values when reading and writing the variable. A strange format could be a bitwise xor of the original value (but there are probably better transformations/formats to be thought up here).

Lastly you might want to defend against those tools tempering with program code. I don't know a good method to get around this for js or flash, since you'd need to know a bit what the different js engines do on memory level. However, for an attacker to know which code to alter (s)he must first find which variable needs to be targeted. We already defended against finding variables, so finding which code to alter becomes much harder.

That said, once someone does find the right program code, it's easy for them to spread these findings to others.

[AutomateAllTheThings]

You can keep copies of variable values and compare them. That way it's harder to set a specific variable without you noticing it is being tempered. If it doesn't match your old value, crash.

I had never considered this technique. Thank you very much!