|
When W32.Opaserv.Worm runs, it does the following:
It checks for the value
ScrSvrOld
in the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
If the value exists, the worm deletes the file that the ScrSvrOld
points to.
If the ScrSvrOld value does not exist, then the worm determines
whether the value
ScrSvr
exists in the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
If the value does not exist, the worm adds the value
ScrSvr %windir%\ScrSvr.exe
to that registry key.
Next it checks whether it is being run as the file %windir%\ScrSvr.exe.
If it is not, it copies itself to that file name and adds the
value
ScrSvrOld <original worm name>
to the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
NOTE: %windir% is a variable. The worm locates the Windows
installation folder (by default this is C:\Windows or C:\Winnt)
and uses that as a destination folder.
After the worm checks the registry values and the location from
which the worm is executing, the
worm checks whether it is currently executing by creating a mutex
with the name ScrSvr31415.
If it is not already executing, the worm registers itself as
a process under Windows 95/98/Me. Under Windows NT/2000/XP it
elevates the priority of the worm process.
The worm then inventories the network looking for "C\"
shares. For each share that it finds, it copies itself to C\Windows\Crsvr.exe.
The worm modifies C:\Windows\Win.ini by adding the line
run= c:\tmp.ini
It also creates C:\Tmp.ini, which contains the text
run= c:\windows\scrsvr.exe
The worm also appears to be able to update itself by reading
files from a Web site whose URL is
hardcoded within the worm. It also attempts to download an update
named Scrupd.exe.
|