Report On Techniques To Prevent Byte Hacking

We have a small application who's EXE was recently modified to jump around specific anti-debugger and timebomb checks, thus subverting our security. We would like a detailed report which educate us more fully on how such techniques could be defeated.

Currently we would like to avoid discussions on packers, and code encryptors etc and focus soley on how check points could be obfuscated so that they are more difficult to detect, and harder to subvert.

For example attached is a small snippet describing the hack. We would like to understand how the call to our check could have been obfuscated, hidden, protected etc.

Thanks in advance for your time.

## Deliverables

1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.

2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):

a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.

b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.

3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).

## Platform

win2k+ VC++

Assembly C Programming Engineering MySQL PHP Software Architecture Software Testing

Project ID: #3952575

About the project