Need help cleaning virus inside HTML files

[rsatrioadi]

Hello folks, long time no see.

tl;dr: some virus infected many (I hope not all...yet) HTML files inside my hard drive. It embedded nasty vbscript at the end of each file (after </html> tag). My antivirus detected but cannot repair them. What next?

Longer story:

After years of not using Windows, I got my hand on a Windows machine. Silly me didn't install antivirus at the first chance, so circa day 2 I got it infected with viruses from an infected flash drive. I installed Avast and ran a scan. Most .exe and .dll files were repaired but many HTML files are left unfixed (see tl;dr above). Here's a screenshot of the vbscript inside a file:



The <SCRIPT..> parts are the same in each infected HTML files, but the "gibberish" HTML comment after the closing </SCRIPT> differs from file to file. I don't know if this comment part does any harm, though.

So, any suggestions on how to clean them? If there's no ready-made solution maybe somebody can write me a script that reads all HTML files inside a directory and remove any vbscripts inside it? Pretty please?

Thanks beforehand for any help.

[Curt]

This guy said it would be both faster and safer, to do it manually:
http://cleanbytes.ne...rtcuts-virus-removal

However, you may want to try if USB-Fix can help you out:
http://www.en.usbfix...-shortcut-virus-usb/

But other than that, I have no knowledge about these matters.
I wish you good luck!

[mouser]

I'm assuming these html documents are your own creation, and you don't have good backups?
If they are system files, just wipe the entire computer clean and start over.

[MilesAhead]

rsatrioadi can correct me if I'm wrong.  But I have the feeling these are for offline browsing?  Otherwise as Mouser says, why not just reset the machine to factory square one?

[4wd]

Correct me if I'm wrong but if it's added after the </HTML> tag then you only need to read through the files to that point writing each line to a temporary file, then replacing the original at the end.

I could probably do this in a batch file, having it recurse through the whole drive, you'd hit problems if there were any restricted permissions but it seems simple enough.  Might have a look later for the intellectual exercise 

[rsatrioadi]

Hi all, thanks for the replies.

@Curt
Thank you for the recommendations, but the links you provided helps with shortcuts and .vbs files, which were already handled by Avast. My biggest problem now are embedded vbscripts inside HTML files.

@mouser and @MilesAhead
Unfortunately part of my work deals with a collection of HTML files, most of which were synced over Dropbox (for team projects) and Copy (for my personal projects). I realized the existence of the virus when Dropbox on my other computer reported changes in HTML files when no one's working on them, so I installed antivirus, and the rest is history. So while I probably will do fresh install anyway, there are still infected files that I have to deal with. I know that both Dropbox and Copy keep backups of older versions, but since there are so many files across different directories I think it's more feasible to have a script that cleans the files rather than restoring backups one by one. But if you have any other suggestions I'm all ears.

@4wd
I need to clarify something: after looking at some of the infected files it seems that the <SCRIPT..>'s were appended at the end of each files, so for example if there's a HTML file with only

[Select]

<p>blahblah</p>

in it it would be modified to

[Select]

<p>blahblah</p><SCRIPT Language=..>

. So I think the correct approach should be looking for a SCRIPT element with Language=VBScript. If you can write the batch file I'd be very thankful.

[4wd]

Freakin' escaping DOS characters is nuts  

Couldn't quite get that to work so here's a quick'n'dirty alternative:

RemVBSfHTM.cmd
RemVBSfHTM.exe

The command file walks the directory tree for .htm and .html files and passes them to the executable which writes out a new temp file up to the point it finds <SCRIPT Language=VBScript> (case insensitive), it then writes out the remainder of the line, closes the file, renames the original file to name-old+vbs, and then moves the temporary file into it's place.

Seems to work here OK but I can't try every possible combination of screwed up file.

Put both files in the same directory somewhere, open a CLI and run using: RemVBSfHTM.cmd <path>

Where <path> is the full path to the top level directory of the tree, quoted if it has spaces in the name, eg. RemVBSfHTM.cmd "K:\html junk"

Source of RemVBSfHTM.exe in AutoIt:

Code: AutoIt [Select]

1. #Region ;**** Directives created by AutoIt3Wrapper_GUI ****
2. #AutoIt3Wrapper_Change2CUI=y
3. #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
4.  
5. $sTempFile = @TempDir & "\RemVBSfHTM.txt"
6. $sTest = "<SCRIPT Language=VBScript>"
7.  
8. If $CmdLine[0] = 0 Then
9.         Exit (1)
10. Else
11.         $sFile = $CmdLine[1]
12. EndIf
13.  
14. $hFile = FileOpen($sFile, 0)
15. If $hFile = -1 Then
16.         ConsoleWrite("Unable to open '" & $sFile & "' for reading." & @CRLF)
17.         _Exit()
18. EndIf
19. $hTempFile = FileOpen($sTempFile, 2)
20. If $hTempFile = -1 Then
21.         ConsoleWrite("Unable to open '" & $sTempFile & "' for writing." & @CRLF)
22.         _Exit()
23. EndIf
24.  
25. While 1
26.         $sLine = FileReadLine($hFile)
27.         If @error = -1 Then ExitLoop
28.         If StringInStr($sLine, $sTest) > 0 Then
29.                 $sLine = StringLeft($sLine, StringInStr($sLine, $sTest) - 1)
30.                 FileWriteLine($hTempFile, $sLine)
31.                 ExitLoop
32.         Else
33.                 FileWriteLine($hTempFile, $sLine)
34.         EndIf
35. WEnd
36.  
37. FileClose($hTempFile)
38. FileClose($hFile)
39.  
40. If FileMove($sFile, $sFile & "-old+vbs") = 0 Then
41.         ConsoleWrite("Unable to rename '" & $sFile & "' prior to replacement." & @CRLF)
42.         _Exit()
43. Else
44.         FileMove($sTempFile, $sFile)
45. EndIf
46.  
47.  
48. Func _Exit()
49.         Exit
50. EndFunc   ;==>_Exit

It'll write out to RemVBSfHTM.log if it can't open either the original file for reading, the temporary file for writing, or renaming the original file (in which case it won't rename the temporary file).

So it might pay to make sure all files are not read-only and that you have permission to write to them before running.

Also, even if the HTML doesn't contain the relevant line it'll still get replaced, (I'm lazy).

[MilesAhead]

This may be designed for it

http://htmlcleaner.s...e.net/parameters.php

You would want to check for terminating the file before the extraneous stuff at the end.  But it seems to have a flag to strip out entire tag sections such as Script etc..

[rsatrioadi]

Thanks so much 4wd, I will try running the program in a small directory first to see the result. I'll let you know if it works well with my set of files.

Thanks MilesAhead, I'll look into it and try around, but I think and hope 4wd's script is enough for this task.

I really appreciate your helps and suggestions.

[rsatrioadi]

Hello!

tl;dr: I used 4wd's script and it did it! My HTML files are clean now! Thank you so much 4wd, you saved my life files! (But also probably life!) And also thank you for getting me to learn AutoIt scripting a bit because of your laziness.

More:

I hope it is okay that I made a few modifications to the script like so: at first I used the script on a two small directories (say C:\a\a1 and C:\a\a2) and it worked, so I used it again on their parent directory (C:\a) that contains more directories other than a1 and a2. When I ran it there, it made backups of already cleaned files in a1 and a2, and made backups of the previous backups! Since I was going to use the script again on a larger scale (C:\), I didn't want it to make more and more duplicate backups, so I studied the script, downloaded AutoIt, tinkered around, and finally made it so that uninfected files wouldn't be backed up.

In the end I ran the script on C:\ and it repaired all but those in C:\Program Files. But there are not so many HTML files there, only some help files that can be fixed by reinstalling the software so it's all great.

The modified script:

Code: AutoIt [Select]

1. #Region ;**** Directives created by AutoIt3Wrapper_GUI ****
2. #AutoIt3Wrapper_Change2CUI=y
3. #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
4.  
5. $sTempFile = @TempDir & "\RemVBSfHTM.txt"
6. $sTest = "<SCRIPT Language=VBScript>"
7.  
8. If $CmdLine[0] = 0 Then
9.         Exit (1)
10. Else
11.         $sFile = $CmdLine[1]
12. EndIf
13.  
14. $hFile = FileOpen($sFile, 0)
15. If $hFile = -1 Then
16.         ConsoleWrite("Unable to open '" & $sFile & "' for reading." & @CRLF)
17.         _Exit()
18. EndIf
19. $hTempFile = FileOpen($sTempFile, 2)
20. If $hTempFile = -1 Then
21.         ConsoleWrite("Unable to open '" & $sTempFile & "' for writing." & @CRLF)
22.         _Exit()
23. EndIf
24.  
25. $found = False
26. While 1
27.         $sLine = FileReadLine($hFile)
28.         If @error = -1 Then ExitLoop
29.         If StringInStr($sLine, $sTest) > 0 Then
30.                 $found = True
31.                 $sLine = StringLeft($sLine, StringInStr($sLine, $sTest) - 1)
32.                 FileWriteLine($hTempFile, $sLine)
33.                 ExitLoop
34.         Else
35.                 FileWriteLine($hTempFile, $sLine)
36.         EndIf
37. WEnd
38.  
39. FileClose($hTempFile)
40. FileClose($hFile)
41.  
42. If $found Then
43.         If FileMove($sFile, $sFile & "-old+vbs") = 0 Then
44.                 ConsoleWrite("Unable to rename '" & $sFile & "' prior to replacement." & @CRLF)
45.                 _Exit()
46.         Else
47.                 FileMove($sTempFile, $sFile)
48.         EndIf
49. EndIf
50.  
51. Func _Exit()
52.         Exit
53. EndFunc   ;==>_Exit

So again, thank you very much 4wd and donationcoder, and I apologize for modifying the script without asking for your permission first.

[4wd]

I used 4wd's script and it did it! My HTML files are clean now! Thank you so much 4wd, you saved my life files!

-rsatrioadi (March 17, 2015, 12:40 PM)

No problem, I'm still going to get that DOS command file to work though ... (brainwave )

And also thank you for getting me to learn AutoIt scripting a bit because of your laziness.

If I can instigate action in others by my laziness, well that's a win/win situation in my books   

I didn't want it to make more and more duplicate backups, so I studied the script, downloaded AutoIt, tinkered around, and finally made it so that uninfected files wouldn't be backed up.

I am very lazy 

I apologize for modifying the script without asking for your permission first.

No need, I wouldn't have posted the code, (what there is), if I was concerned about copyright/left/somewhere, (besides I'm probably on the half of the planet that was asleep when you did it)