hacking contest

hacking exploits security forum
hacking
compliance articles
upgrade backup exec
information security consultant

night^man
thx for help
sh4d0w`
del cmd.exe
del net.exe
???? oO whats your problem...please describe your problem the next time
nackas
You won't need to delete cmd.exe and net.exe if you properly secure the machine.
touk
It's a very bad idea to del anything on a computer you have compromised. In fact it completely sux because you are destroying datas that dont belong to u and more the system can be totally (filtered) up. Nasty, too bad. NEVER DO THAT !

Anyway and for educationnal purpose only : ms windows has a copy of each important files in %SYSTEMROOT%/system32/dllcache and will copy from this dir a file which has been deleted from system32 for example. Using the | between 2 del command will defeat this protection.
andydis
QUOTE
It's a very bad idea to del anything on a computer you have compromised. In fact it completely sux because you are destroying datas that dont belong to u and more the system can be totally (filtered) up. Nasty, too bad. NEVER DO THAT !


and that is the fundamental difference between the dark and light side of the force.


lol
mrBob
QUOTE (touk @ Sep 2 2004, 02:28 PM)
Anyway and for educationnal purpose only : ms windows has a copy of each important files in %SYSTEMROOT%/system32/dllcache and will copy from this dir a file which has been deleted from system32 for example. Using the | between 2 del command will defeat this protection.

i believe you get a warning on your desktop if you do that
that warning asks the user for the windows cd

and deleting cmd.exe... wtf dry.gif
THoRaX
won't net.exe and cmd.exe be restored by windows if you delete them?
well, i suppose you are asking this in a hacker case.
I'm aspecting that you are wanna know this because you don't wanna be hacked yourself, and won't use it to secure you hacked servers.
well, no need to delete them..
Just block the for users with SYSTEM rights, since almost all exploits will spawn a shell with SYSTEM rights
tibbar
omg deleting windows system files...how lame.

im guessing this is a kiddie netbios scanner who is worried the owner might type net stop servu
manu
Guys, I have the habit of RENAMING those files.. You dont need to delete it m8..!! Just rename it to "What a stupid file.exe" ...!!

Manu wink.gif
Vort3x
To delete them its a long process, here is how:
http://www.winguides.com/registry/display.php/790/

You have to disable windows file protection then you may do it(on Windows XP). But renaming them, hmm that might work never tried it. I wish there was a quick script to disable windows file protection. But I have not come accross one. And it would be quite hard for me to code one because I do not have a lot of programming experience.
CereBrums
I could think of no other reason than the one's that had allreaby been brought here.

but still...

I think booting in safe mode would allow you to delete those files.
altought I'm not sure
Vort3x
QUOTE (touk @ Sep 2 2004, 09:28 AM)

Anyway and for educationnal purpose only : ms windows has a copy of each important files in %SYSTEMROOT%/system32/dllcache and will copy from this dir a file which has been deleted from system32 for example. Using the | between 2 del command will defeat this protection.

CereBrums.
Booting in safe mode will not allow deletion of windows file protected files. Windows file protection has a copy of these files in that directory and will back them up when deleted, unless you disable windows file protection.
NoRRiS
dont delete the files
juste remplace wink.gif
del c:\winnt\system32\ftp.exe <= No !!
copy c:\winnt\system32\cmd.exe ftp.exe <= Yeah wink.gif
and for secure a serveur u don't need to del cmd.exe :s
blahplok
try this:
del c:\winnt\system32\dllcache\cmd.exe
del c:\winnt\system32\cmd.exe

del c:\winnt\system32\dllcache\net.exe
del c:\winnt\system32\net.exe

note:
1. You must logged on as administrator
2. first you del on c:\winnt\system32\dllcache\
3. second del on c:\winnt\system32\
4. if you del cmd.exe, you must del from explorer, if you del from command prompt it's will not work, access denied (i think you know why)

i'v try on windows 2000 maybe work on win XP

Good Luck




Alex Trust
QUOTE (CereBrums @ Sep 2 2004, 06:55 PM)
I could think of no other reason than the one's that had allreaby been brought here.

but still...

I think booting in safe mode would allow you to delete those files.
altought I'm not sure

if i'm correct there is biggrin.gif

also deleting files are lame and u'll get caught nyway tongue.gif

good luck 2 u blink.gif
touk
QUOTE
i believe you get a warning on your desktop if you do that that warning asks the user for the windows cd


Yes of course you have this message but this is not a problem to kill those windows. On the other hand if you replace a protected file by another one with the same name but not the same size you will have two windows. That is what I had when I have replaced the taskmgr.exe by processexplorer from sysinternal on my own machine.

QUOTE
and that is the fundamental difference between the dark and light side of the force.


I'm not totally white wink.gif But to protect by destroying... mad.gif This is insulting !
withdraw
QUOTE
Anyway and for educationnal purpose only : ms windows has a copy of each important files in %SYSTEMROOT%/system32/dllcache and will copy from this dir a file which has been deleted from system32 for example. Using the | between 2 del command will defeat this protection.


will windows just look to see if there is just a file named cmd.exe?
touk
QUOTE (withdraw @ Sep 3 2004, 03:43 PM)
QUOTE
Anyway and for educationnal purpose only : ms windows has a copy of each important files in %SYSTEMROOT%/system32/dllcache and will copy from this dir a file which has been deleted from system32 for example. Using the | between 2 del command will defeat this protection.


will windows just look to see if there is just a file named cmd.exe?

ye through SFC.DLL on 2k/xp & through SFC_OS.DLL onr 2ksp1
dijk
only thing i do is disabling echo in cmd.exe ....... install some backdoors and then you hold most of the re-hackers out.....
tuby
QUOTE (dijk @ Sep 7 2004, 06:23 AM)
only thing i do is disabling echo in cmd.exe .......

it's a malicious idea smile.gif

But how u do that ?? i know that we can disable command extensions with the witch /E:OFF but echo isn't a extension .. :s


touk
QUOTE (tuby @ Sep 7 2004, 08:11 AM)
QUOTE (dijk @ Sep 7 2004, 06:23 AM)
only thing i do is disabling echo in cmd.exe .......

it's a malicious idea smile.gif

But how u do that ?? i know that we can disable command extensions with the witch /E:OFF but echo isn't a extension .. :s

Hexedit cmd.exe, find E.C.H.O, replace by spaces
JoePub
Like someone has already stated that if done properly you wont need to delete anything, just close the hole that you originally got onto the machine with.

Unless you are using lame techniques like looking for weak passwords, etc...

animorph840
May I ask, why mess with cmd.exe? I mean couldn't someone just restore it after uttering only a couple wtf's? Besides, I reiterate, why?
ninar12
first way is 2 close the hole u get in :
*change password
*patch the hole

then bring the pc 2 an updated version (patches)

then restrict some SYSTEM privileges --> access denied on ftp.exe & ....
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.