VBS script virus VBS big number of well-known functions that we have a brand new understanding, it truly is now additionally,
Office 2007, it began to pay out attention to it. VBS code locally by Windows Script Host (WSH) interpreted. VBS script execution can not do without WSH, WSH supplies a Microsoft-based 32-bit Windows platform, and language-independent mechanism to clarify the script, which can make the script straight inside the Windows desktop or command prompt. Using WSH,
Office 2007 Product Key, customers can manipulate the WSH object, ActiveX objects, registry and file system. In Windows 2000, WSH may also be employed to entry the Windows NT Active Directory service. 
 having a VBS script published in the document window interface interpreted by wscript.exe, and cscript.exe file inside the character interpreted from the interface. wscript.exe is really a scripting language interpreter, is that it makes the script can be executed, because the implementation with the very same batch. About VBS we have to know a lot more than I do, so do not bullshit, directly to the topic, see my summary of VBS inside the system safety Magical bar. 
 one, towards the registry editor to unlock 
 use Notepad to edit the following: 
 DIM WSH 
 SET WSH = WSCRIPT.CreateObject ( WSH.POPUP ( 'pop-up message  one. WSH.Regwrite  DisableRegistryTools  'to the registry editor to unlock 
 WSH.POPUP ( 'pop-up concept  conserve to. vbs file extension, use double click on. 
 2nd, flip off the default Win NT/2000 sharing 
 use Notepad to edit the following: 
 Dim WSHShell 'define variable 
 set WSHShell = CreateObject ( Dim fso, dc 
 Set fso = CreateObject ( set dc = fso.Drives' accessibility to all drive letter 
 For Each and every d in dc 
 Dim str 
 WSHShell.run ( next 
 WSHShell.run ( WSHShell.run ( now to test, initial open the cmd.exe, enter the net share command to see their share on the machine. Double click to run stopshare.vbs, will see the window flash off. Then in cmd, enter net share command, this time sharing the checklist didn't get the 
 1. New Roman  III shows the neighborhood IP tackle 
 quite a few occasions,
Office Professional 2010, we need to know the machine's IP tackle, even though could be done using different software, but having a VBS script is also especially convenient. Use Notepad to edit the subsequent: 
 1. Dim WS 
 2. Set WS = CreateObject ( three. IPAddress = WS.LocalIP 
 four. MsgBox  preserve the contents with the previously mentioned ShowIP.vbs, double-click the implementation with the nearby IP handle can be obtained. 
 Fourth, using scripting deletion log 
Right after the success of the invasion method  the very first factor hackers do is apparent the log, the remote control if your other graphical interface or from your terminal logged in to the machine, delete the log is not a challenging job,
Windows 7 Download, though it's got also, because of the log service is operating, but in contrast to http, ftp this services, you possibly can quit in the command line, then eliminate the command line using web quit eventlog can not be stopped, so some individuals think the command line is highly tricky to get rid of the log the fact is not the case, for instance, use the script in the VMI system can delete the log, but also very uncomplicated and hassle-free. Supply code is as follows: 
 one. strComputer =  two. Set objWMIService = GetObject ( 3. &  four. strComputer &  5. dim mylogs (three) 
 6. mylogs (1) =  7. mylogs (two) =  8. mylogs (3) =  9. for Each and every logs in mylogs 
 10. Set colLogFiles = objWMIService.ExecQuery _ 
 11. ( 12. For Every objLogfile in colLogFiles 
 13. objLogFile.ClearEventLog () 
 14. Subsequent 
 15. subsequent 
 previously mentioned code will save cleanevent.vbs files. Inside the above code, very first receive the object object, and then use its clearEventLog () technique to delete the log. Create an array, application,
Cheap Office 2010, security, system, if there are other logs can also add an array. Then with a for loop, get rid of just about every element from the array, the individual logs.