News
100 Paper Clips Founded and PCP Hacker v1.0 Alpha Released
- Details
- Published on Monday, 11 February 2008 01:05 Geoff McDonald Hits: 408
Today 100 Paper Clips has first come online featuring a new type game hacking utility I am working on.
Paper Clip Function Hacker (PCP Hacker) v1.0 Alpha: This new tool hacks games from a different approach; function searching. It works by attaching to the specified game, disassembling all the code, then redirecting all call instructions to fake 'call logger' functions which logs the call then makes the real call. This allows you to search for functions based on how many times they were called. I have already implemented a couple more advanced features allow you to record the arguments on the stack for function calls, and nop'ing a function. Nop'ing a function just takes the ret** instruction from the function and places it at the start of the function to maintain stack integrity. Also an order functions feature has been implemented, allowing you to determine the order of multiple function calls. In summary it currently allows you to:
- Filtering functions based on number of calls.
- Filtering functions based type of calls (All, or inter-module calls)
- Recording the stack when a function is called (Is used to determine the arguments to the function)
- Viewing the assembly of the function and it's callers to determine the function arguments.
- Sorting multiple functions to determine their call order. This is used to figure out how deep the function is, the first called function is likely the one you are interested in.
- "nop'ing" a function. If you "nop" a function the function will not do anything, but it will maintain stack integrity.
Right now it intercepts all long fixed-offset call statements. It does not intercept calls off registers or calls with assembly statements without a length of 5 bytes. The performance of the target application is affected, but not significantly due to the low number of instructions added per call statement.
Known Issues:
It is known to crash the target application when the target application closes a standard windows form. I am working on resolving this issue, if you know why this might be, please let me know.


Geoff
Posted at 2011-08-27 16:37:45
Test
Reply to comment