Worm:W32/Dabber.A only affects systems that had been previously infected by Worm:W32/Sasser, as it spreads through a vulnerability in the FTP server of the Sasser worm. Once installed, Dabber removes registry values installed by other malware and installs its own backdoor.
Manual disinfection of Dabber consists of the following steps:
Computers infected by the Dabber worm must also be disinfected of the Sasser worm as well. For disinfection details and a removal tool, please see the Worm:W32/Sasser description.
Find the latest advice in our Community Knowledge Base.
See the manual for your F-Secure product on the Help Center.
Submit a file or URL for further analysis.
Worm:W32/Dabber was written in the Visual C++ programming language, and spreads in a UPX + Pe_Patch compressed form. The unpacked size of the worm is around 70 KiB. Once active on the infected machine, Dabber opens 9898/TCP and installs a general purpose backdoor that can be used to download and execute arbitrary programs.
Also, in an attempt to disable different other viruses, Dabber removes a large number of registry values.
When Dabber enters the system, it creates a copy of itself in the Windows System Directory, using the file name 'package.exe'. This copy is added to the Registry as
Two additional copies are placed to the common user Startup Directories, also using the name 'package.exe'.
Dabber spreads by exploiting a vulnerability in the FTP server of Sasser.
The worm scans random hosts for open 5554/TCP ports, where the Sasser FTP server also listens. If the port is open, Dabber attacks the host with an exploit that opens a shell on the host on 8967/TCP.
Using the shell, Dabber forces the victim machine to download the worm body from the attacker host using TFTP. Dabber has its own TFTP server to serve the victims. Summary of TCP ports used by the worm: