Additional Details
The worm installs itself to the Windows directory with the name
"scrsvr.exe" and registers this file in the system registry's
auto-run key:
HKLM\Software\Microsoft\Windows\CurrentVersion\Run
ScrSvr = %worm name%
Opasoft then deletes its original file (from where it was
started).
In order to find victim computers Opasoft scans subnets for port
137 (NETBIOS Name Service). IP addresses of the following
networks are scanned:
* current subnet of the infected computer (aa.bb.cc ??)
* the two nearest subnets of the currently infected computer (aa.bb.cc.cc+1 ?? , aa.bb.cc-1 ??)
* selects subnets randomly (excluding those where scanning is disabled)
If while searching (scanning) Opasoft happens upon a responding
IP address (of an actual computer), the worm then scans the two
nearest subnets of that IP address.
When "reply data" is received, Opasoft checks the special field
that it contains. If it shows that the given computer has the
service "File and Print Sharing" open, Opasoft begins its
infection procedure on that computer as a remote host.
During infection, Opasoft sends, via port 139 (NETBIOS Session
Service) special SMB - packets that transmit the following
commands:
1. sets a connection with the \\hostname\C resource, where
"hostname" = the name of the victim computer which is defined
when the victim computer answers Opasoft (by sending its "reply
data") during the scan
2. if the resource is password-protected the worm runs through
all possible "one symbol" passwords - conducting a "brute-force"
attack
3. if connection is successful, Opasoft transmits its EXE file -
during transmission the full name of the destination file
containing the code (exe file) is revealed:
WINDOWS\scrsvr.exe
4. Opasoft then reads the Windows\win.ini file on the victim
machine and copies (saves) it to the local disk (of the remote
computer) under the name:
C:\TMP.INI
5. the worm adds auto run command for the dropped EXE file to
C:\TMP.INI file the wormand copies it back to the victim computer
To receive the packets from the remote computer two files appear
on the victim machine:
\WINDOWS\scrsvr.exe - a copy of the Opasoft worm
\WINDOWS\win.ini - A Windows INI file which contains the auto-run command (to "auto-run" the Opasoft worm)
The second file, WIN.INI, results in Opasoft gaining control of
the victim computer upon system restart.
To get passwords needed to gain access to victim machines, the
worm uses the security breach "share level password exploit". For
a detailed description of this exploit please click the following
page:
http://www.nsfocus.com/english/homepage/sa_05.htm
The worm programmatically "suggests" a password field with only
one character length to the victim host. When there is a one-byte
password "suggested", the host will check only the first byte of
the password. In case the first byte is correct, the
authentication process will be successfully completed. As a
result it is enough to try only all one-byte passwords for the
attacker to exploit vulnerable Win9x machines. The patch for this
vulnerability is available at:
http://www.microsoft.com/technet/security/bulletin/MS00-072.asp
The backdoor routine goes to the www.opasoft.com WEB-site and
performs the following actions:
* downloads and executes its latest version (if there is one)
* downloads and processes script files placed at this site
New worm versions are downloaded to the file "scrupd.exe". This
file is then run, and replaces the existing worm copy.
While processing the backdoor uses its data files: "ScrSin.dat"
and "ScrSout.dat". These files are encrypted with a strong
crypto-algorythm.
Because the server at www.opasoft.com is down, it is not possible
to get more information about this backdoor routine.
To avoid double twice on the same machine the worm creates a
"Windows mutex" under the "ScrSvr31415" name.
Win9x machines are infectable while the infectinon of WinNT-based
machines is highly unlikely and almost impossible.
One of worm versions writes log data about scanned and infected
machines to the "ScrLog" and "ScrLog2" files.
The worm caused a global outbreak and hit many Win9x systems
because of following reasons:
* it spreads using the standard NETBIOS protocol
* the "\\hostname\C" resource name is the default name on opening a share on C: drive
* there is no request for a password on share opening
* many users don't pay enough attention to password length and security
To get rid of the worm and to avoid reinfection it is necessary
to:
* disable file sharing, or apply safe enough password to opened shares
* delete infected EXE file
* remove worm's "run" commands from WIN.INI file and system registry (see above)
F-Secure Anti-Virus detects Opaserv worm with the following
updates:
[FSAV_Database_Version]
Version=2002-10-01_02
| VARIANT: | Opasoft.A |
| ALIAS: | Worm.Win32.Opasoft.a, Brasil |