Pages: 1, 2, 3, 4, 5
tibbar
30 days from 1st installation of trial i think!!
phaeton
Well I can safely say my version is not time-bombing. I don't know if its detected by KAV (I need to find someone with it) but I know its not timebombing right now. I'll let you know more once I get it scanned on a KAV machine.
tibbar
out of interest, open your server in a resource editor, and see if you can spot the time countdown...if its the proper version it will be 69kb.

the time out version is 71kb.
Ment0r
first of all

THX 4 this very kewl info ;-)

But with my luck it doesn't work...

I used your instructions and successfull created the .exe file, where I've changed the variables .... My Norton AV 2004 also said "Hack Defender Virus" .....
jedi
thx biggrin.gif
very useful tuto cool.gif
ako
i'll have a go at this good work mate biggrin.gif
phaeton
Ment0r, you messed up somewhere. I think I forgot to say you need to change the name of the logfile... and the mailserver lines etc etc.

Tibbar, 69KB here =D And I'm using 7 Trial -> Enterprise patch.

Still haven't gotten it done on KAV though. Need to find someone...
Jipsu
yup.. 69KB here too and using the same delphi "patch" as phaenton.. And mine doesn't get detected by KAV smile.gif
phaeton
Jipsu did you follow my guide or did you do something else?
tibbar
ok this is interesting...

i tried two compile methods.

1) on legitimate delphi 7 enterprise, from install cd...

result KAV detects it.

2) on trial + crack... undetected by KAV.

it seems that the cracked trial must leave some residual time code that doesnt run in the .exe, which hides it from KAV.
Jipsu
QUOTE (phaeton @ Feb 5 2004, 11:21 PM)
Jipsu did you follow my guide or did you do something else?

Just followed your guide biggrin.gif
phaeton
Ok good smile.gif Last time I checked it was bypassed by KAV, so some people must be doing something wrong =D
Ment0r
@phaeton

i changed the values successfull

CODE

ServerMailslotNamePart='\\.\mailslot\gelee-gl100s';
ClientMailslotNamePart='\\.\mailslot\gelee-glc';
DriverDeviceName='\\.\geleeDriver';
......
geleeLogFileName='c:\winnt\system32\rootkit.log';



but exe got detected by NAV 2004
tibbar
i dont dispute that the compile file from the cracked delphi 7 trial is undetected.

all im saying is if you recompile it on the legitimate delphi 7, it is detected by KAV.
phaeton
mentor, make sure you change all RK_ values also, and all other hxdef strings
Ment0r
didn't find any more RK_ variables, everything seems ok, don't know ^^
mofo
i'd reward someone who hexs my kit.
phaeton
Why would you need to hex a kit? Mine is 100% undetectable and I just recompiled it.
zero-maitimax
mmm. i just add some byte's an pack it with upx and olso it isn't detected..



Neo2k
nice post dude ... I was looking for a tut on hxdef and you post it ^^

THX smile.gif
Skeelow
This still workin ? Think Im gonna give it a shot
phaeton
Yessir Skeelow, still works smile.gif (modifying the source never gets old biggrin.gif)
MChakaL
Hello, I would like to know how to as hide file known ftp, i.e., as in the list (ex: /c:/winnt/system32/hxdef100.exe ) one do not see them smile.gif
tianzhen
QUOTE (zero-maitimax @ Feb 16 2004, 11:20 AM)
mmm. i just add some byte's an pack it with upx and olso it isn't detected..

really? u mean by kav? or what..
phaeton
mchakal: can you be a bit more specific, sorry I couldn't understand what you said...
white
nice!
gephorce
Great Tutorial
Thanks for sharing!
rrs
latest symantec update detects the modified version now sad.gif
guufa
Good tut, but now the rootkit is detected by nav.
phaeton
Interesting, I'll take a look @ it when I get a chance.
DCLXVI
mine is still undetected by norton , only detected by kav biggrin.gif
jtevermore
it's detecting the switch initializer.

change it.
phaeton
there is another reference to hxdef there.... in .\Device\UDP\.\?.?\HxDef, also it could be detecting names of the fields in .ini, also switches could be detectable too smile.gif I'll try too update this thread with what needs to be changed after I go through it all.
MtM
I made mine undetected by McAfee and NAV as of March 1st. There are a crapload of things you need to change. Also, it looks like any file packed with morphine is now detected by McAfee as virii, wether it's virii or not :-( That really really sucks.
axora
QUOTE (phaeton @ Jan 30 2004, 04:52 PM)
Next, there are lines like these:
CODE

ServerMailslotNamePart='\\.\mailslot\hxdef-rk100s';
ClientMailslotNamePart='\\.\mailslot\hxdef-rkc';
DriverDeviceName='\\.\HxDefDriver';


Here your hxdef will already be changed thanks to the first step, but the "-rk*" needs to be changed to a "-**" where "**" is any 2 character string.

Do i only have to change the "-rk*" in these 2 lines or also in the other lines where "-rk*" is in?
For example:
CODE

BackdoorMailslotName:='\\.\mailslot\hxdef-rks'+IntToStr(LInt64);
phaeton
you need to change all the rk- instances (and hxdef too)
Killaloop
QUOTE (MtM @ Mar 1 2004, 05:38 PM)
I made mine undetected by McAfee and NAV as of March 1st. There are a crapload of things you need to change. Also, it looks like any file packed with morphine is now detected by McAfee as virii, wether it's virii or not :-( That really really sucks.

Yep too true
mcaffee deletes every morphine packed file, but I think they will remove this by the next update cause this is kinda stupid I would say. Also they added some serv-u versions in there list. keeps deleting half of my files from hdd but most of them are nothing (services.exe to show me service list for example...)
lame ass AV ^^
tianzhen
http://yousmelllikeshit.com/files/hxdef-builder-3.rar

with this u can compile hxdef without delphi vc ddk..
axora
I changed the driver source files und tried to build a new driver.sys with DDK.
DDK gives no errors and compiles. But there is no new driver in /objfre/386 !?

Edit: Already fixed that prob. It was the jvc problem.
axora
Should I also rename the new hxdef.exe?
If yes: Rename it with the same characters that replaced "hxdef" in source?
tianzhen
F:\hxdef-builder-3>comp\dcc32 -Udcus;units hxdef100.dpr

Borland Delphi Version 15.0
Copyright © 1983,2002 Borland Software Corporation
hxdef100.dpr(15) Fatal: File not found: 'USysUtils.dcu'



and there is on 'USysUtils.dcu' no in the hxdef100.zip where to get 'USysUtils.dcu' help plz..



//edit found it ,this one with src.zip http/rootkit.host.sk/release/hxdef100.zip
phaeton
axora the name of the exe doesnt matter.

and that hxdef builder is hosted on my site smile.gif
r1dg3d
wow. much appreciation for this. Had been curious how to do so but didn't know where to start, thanks again. *goes off to fiddle*
metrox
thanks for the info, it´s so easy to make a (anti-vir) trojan and rootkit, with a little bit modifications, thanks

metrox
Toxi
phaeton:
Thank you for this really good, easy and working tutorial.

Finally I worked out some time to test this. Everything is working fine but rdrbs100.exe is detected by NAV 2004 Pro.

Anyone got rdrbs100.exe undetected and could give little tips what to modify?

And should I also modify bdcli100(backdoor client)? Because nav detects it in original pack.
axora
Works fine now. Thanks for tut.
ch0pper
as of the 31 march macaffe enterprise virus defintions :4346 scan engine :4.3.20 compled hxd
are picking up all versions hxd source code and driver
can not seem to work out what they are pickig up as yet and one else found this ! think they have changed there check sum strings
phaeton
When you view sources of hxdef, and change all references, looks good, but check the hex of the compiled exe, still reference to hxdef in one line wink.gif change that... also change switch names (helps if other user finds your hxdef ;P), also it doesnt hurt to change non api strings so they cant find it in the future smile.gif gl

rush
NAV is detecting the driver for some while know (edited with the method mentioned above). Any idea how to make it undetecable again?
Killaloop
I got no problem to hide the files from NAV (enterprise edition). but mcaffe picks up the driver for some reason. I don't seem to get it ..
anyone knows what mcaffe looks for? changed alot without luck
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.

 
Invision Power Board © 2001-2005 Invision Power Services, Inc.