Creating executable Trainer undetectable by Xtrap

Well come post a source for those who want to help and do hackers bypass Xtrap

she mentioned this to better learning of you


[Only registered and activated users can see links. Click Here To Register...]

Quote:

---

unit Unit1;

interface

uses
Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
Dialogs, StdCtrls, XPMan, TlHelp32, ExtCtrls, ShellApi;

type
TForm1 = class(TForm)
XPManifest1: TXPManifest;
Timer1: TTimer;
GroupBox1: TGroupBox;
CheckBox2: TCheckBox;
CheckBox3: TCheckBox;
CheckBox6: TCheckBox;
Label1: TLabel;
Label2: TLabel;
procedure FormCreate(Sender: TObject);
procedure Timer1Timer(Sender: TObject);
procedure Label1Click(Sender: TObject);

private
{ Private declarations }
public
{ Public declarations }
end;

var
Form1: TForm1;
implementation
function GetPidByName(ProcessName : string):DWORD;
var
Process : DWORD;
ProcessEntry : TProcessEntry32;
begin
Result := 0;
ProcessEntry.dwSize := SizeOf(TProcessEntry32);
Process := CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0);
if (Process32First(Process, ProcessEntry)) then
repeat
if (lstrcmpi(ProcessEntry.szExeFile,PChar(ProcessName )) = 0) then
begin
Result := ProcessEntry.th32ProcessID;
Exit;
end;
until (not Process32Next(Process, ProcessEntry));
end;
procedure ChangePrivilege(szPrivilege: PChar; fEnable: Boolean);
var
NewState: TTokenPrivileges;
luid: TLargeInteger;
hToken: THandle;
ReturnLength: DWord;
begin
OpenProcessToken(GetCurrentProcess(), TOKEN_ADJUST_PRIVILEGES, hToken);
LookupPrivilegeValue(nil, szPrivilege, luid);
NewState.PrivilegeCount := 1;
NewState.Privileges[0].Luid := luid;
if (fEnable) then
NewState.Privileges[0].Attributes := SE_PRIVILEGE_ENABLED
else
NewState.Privileges[0].Attributes := 0;
AdjustTokenPrivileges(hToken, False, NewState, SizeOf(NewState), nil, ReturnLength);
CloseHandle(hToken);
end;
{$R *.dfm}

procedure TForm1.FormCreate(Sender: TObject);
begin
ShellExecute(handle,'open','https://progamercity.net/forum.php',nil,nil,sw_shownormal);
ChangePrivilege('SeDebugPrivilege',True);
end;

procedure TForm1.Timer1Timer(Sender: TObject);
var
PID : DWORD;
hProc: DWORD;
Value3,Value1 : Integer;
Written : DWORD;
Buffer : Byte;
begin
PID:= GetPidByName('game.exe');
if PID<>0 then
begin
hProc:= OpenProcess(PROCESS_ALL_ACCESS,false,PID);
Value3:= 1;
ReadProcessMemory(hProc,Ptr($00460000),@Buffer,1,W ritten);
if Buffer = $0D then
begin
if CheckBox2.Checked then
WriteProcessMemory(hProc,Ptr($00000),@Value3,1,Wri tten);
if CheckBox3.Checked then
WriteProcessMemory(hProc,Ptr($00000),@Value3,1,Wri tten);
if CheckBox6.Checked then
WriteProcessMemory(hProc,Ptr($00000),@Value3,1,Wri tten);
ExitProcess(0);
end;
CloseHandle(hProc);
end;
end;



procedure TForm1.Label1Click(Sender: TObject);
begin
ShellExecute(handle,'open','https://progamercity.net/forum.php',nil,nil,sw_shownormal);
end;

---

can i have ur facebook pls i wana talk whit u xD
and ty for ur share

i've tried your code, in windows 64 bit it will run successfully but the problem when we use win 32 .. the xtrap caught me >.<

is somewhat difficult to do hacks in the game executables that attack as well easier for dll's

--

é um pouco dificil de se fazer hacks em executaveis que atacam o jogo, bem mais facil em dll's

Quote:

---

i've tried your code, in windows 64 bit it will run successfully but the problem when we use win 32 .. the xtrap caught me >.<

---

Generally with xTrap/Hacksheild etc they have less control over x64 (64bit) than x86 (32bit).
On x86 they generally use a driver/rootkit to do hooks for detection and protection on a kernel level (the core level of windows not usually accessible to a general user) which they can't do as easily on x64's architecture.

I'm not an expert on this subject so if you want to know more search this forum or Google it up :good:

for me, I think better to focus on creating for 64 bit

feeling depressed >.<

I really liked but did not think a good way, just be better in dll because if you can access the memory more easily.

Gostei muito mais n acho uma boa maneira,simplesmente seria melhor em dll ja que se pode acessar a memoria com mais facilidade.