Congratulations on 175PT 3.0.4.5 Update!

[h4c0r-BG]

I want to congratulate on the 175pt developers, for their update.

They do memory checks on their module (like should have been from long time ago).
If you stop their checks hearthbeat, the auth dies (like it should have been, and i think DOKEE used something like that).
If you do memory modifications (corrupt memory CRC) - the auth dies (again).

The only thing is that you should've kept the error kicking after cheat detection instead of an auth failure. This way you wouldn't know from where the problem comes but ... good job on the update.

When i am bored i will look into it deeper. Kind regards, h4c0r-BG.

Originally Posted by h4c0r-BG

I want to congratulate on the 175pt developers, for their update.

They do memory checks on their module (like should have been from long time ago).
If you stop their checks hearthbeat, the auth dies (like it should have been, and i think DOKEE used something like that).
If you do memory modifications (corrupt memory CRC) - the auth dies (again).

The only thing is that you should've kept the error kicking after cheat detection instead of an auth failure. This way you wouldn't know from where the problem comes but ... good job on the update.

When i am bored i will look into it deeper. Kind regards, h4c0r-BG.

Thank you for your answer! Of course! I was not trying to look silly again, you can too! But I still hope you can give a hint! Sincerely, your fans!

Don't forget : just for fun

Originally Posted by 强生cs工作室

Don't forget : just for fun

that's great!

// DWORD Address = 0x1000B512;
DWORD Address = 0x1000C5F2;
BYTE PokeValue = 0xEB;
DWORD NumberOfBytes = 1;
DWORD Write=0;
DWORD HLProcessId=0;

HWND HLwnd=FindWindow(NULL, "Counter-Strike");
if(!HLwnd)
{
MessageBox(hwnd,"wnd", "no wnd", MB_ICONINFORMATION);
return 0;
}
DWORD ThreadId =GetWindowThreadProcessId(HLwnd, &HLProcessId);
HANDLE HandleWindow = OpenProcess(PROCESS_ALL_ACCESS, FALSE, HLProcessId);

WriteProcessMemory(HandleWindow, (LPVOID)Address, &PokeValue, NumberOfBytes, &Write);

MessageBox(hwnd,"ok", "good", MB_ICONINFORMATION);


my code bypass WH BLock , but i got Kick , please help me !!!

Originally Posted by cancoder

// DWORD Address = 0x1000B512;
DWORD Address = 0x1000C5F2;
BYTE PokeValue = 0xEB;
DWORD NumberOfBytes = 1;
DWORD Write=0;
DWORD HLProcessId=0;

HWND HLwnd=FindWindow(NULL, "Counter-Strike");
if(!HLwnd)
{
MessageBox(hwnd,"wnd", "no wnd", MB_ICONINFORMATION);
return 0;
}
DWORD ThreadId =GetWindowThreadProcessId(HLwnd, &HLProcessId);
HANDLE HandleWindow = OpenProcess(PROCESS_ALL_ACCESS, FALSE, HLProcessId);

WriteProcessMemory(HandleWindow, (LPVOID)Address, &PokeValue, NumberOfBytes, &Write);

MessageBox(hwnd,"ok", "good", MB_ICONINFORMATION);


my code bypass WH BLock , but i got Kick , please help me !!!

You Need Bypass CRC Check。
You can try the following places to find 175 memory validation code:
Such as:
Read Breakpoint at 0x1000C5F2.

[h4c0r-BG]

Originally Posted by cancoder

// DWORD Address = 0x1000B512;
DWORD Address = 0x1000C5F2;
BYTE PokeValue = 0xEB;
DWORD NumberOfBytes = 1;
DWORD Write=0;
DWORD HLProcessId=0;

HWND HLwnd=FindWindow(NULL, "Counter-Strike");
if(!HLwnd)
{
MessageBox(hwnd,"wnd", "no wnd", MB_ICONINFORMATION);
return 0;
}
DWORD ThreadId =GetWindowThreadProcessId(HLwnd, &HLProcessId);
HANDLE HandleWindow = OpenProcess(PROCESS_ALL_ACCESS, FALSE, HLProcessId);

WriteProcessMemory(HandleWindow, (LPVOID)Address, &PokeValue, NumberOfBytes, &Write);

MessageBox(hwnd,"ok", "good", MB_ICONINFORMATION);


my code bypass WH BLock , but i got Kick , please help me !!!

You can try digging in the 175Protect.dll threads and analyse the code, and try to fool the auth part that the threads are performing CRC checks.

Originally Posted by gl32

You Need Bypass CRC Check。
You can try the following places to find 175 memory validation code:
Such as:
Read Breakpoint at 0x1000C5F2.

OLLYDBG got detected by 175protect.dll , hl can't run !!!

Originally Posted by h4c0r-BG

You can try digging in the 175Protect.dll threads and analyse the code, and try to fool the auth part that the threads are performing CRC checks.

can you give me address of CRC checks ? analyse the code is very hard !!

[h4c0r-BG]

Originally Posted by cancoder

can you give me address of CRC checks ? analyse the code is very hard !!

Nobody will spoon feed you in the mouth with ready code and addresses, you have to think on your own sometimes.

Also stop doing it for the game-play-with-cheats, do it for the skill and knowledge and forget the game.