ThreatExpert Report: W32.Jeefo, W32/Jeefo, W32/Jeefo-A, Virus:Win32/Jeefo.A, Virus.Win32.Hidrag..

Visit ThreatExpert web site

Close Report

Submission Summary:

Submission details:

Submission received: 13 September 2012, 20:22:44
Processing time: 8 min 36 sec
Submitted sample:

File MD5: 0x77F73626D26BDBBED29ECBF0C9C04765
File SHA-1: 0x8C0C099247AB924D9EE8AD7C6F58AF01694C8B3A
Filesize: 3,554,948 bytes
Alias:

W32.Jeefo [Symantec]
W32/Jeefo [McAfee]
W32/Jeefo-A [Sophos]
Virus:Win32/Jeefo.A [Microsoft]
Virus.Win32.Hidrag [Ikarus]
Win32/Hidrag [AhnLab]

Summary of the findings:

What's been found	Severity Level
Capability to send out email message(s) with the built-in SMTP client engine.
Creates a startup registry entry.
Contains characteristics of an identified security risk.

Technical Details:

The new window was created, as shown below:

NOTICE: The content shown in the above window is captured automatically and is not controlled or endorsed by ThreatExpert.
Please contact us on this link should any material be offensive or inappropriate and we will ensure any such content is blocked from future viewers of the report.

Possible Security Risk

Attention! Characteristics of the following security risks were identified in the system:

Security Risk	Description
Backdoor.ProRAT.K	ProRAT.K is a remote administrative trojan. It allows an attacker to take full control of a compromised computer. It also logs all keystrokes to a text file which can be accessed by the attacker. It also hides itself from task manager and process monitors.
Trojan.Crypt.S	Trojan.Crypt.S is a backdoor trojan which opens a random port and allows hackers to gain unauthorised access to the infected system. It also attempts to terminate antivirus, firewall and other security related processes.
Adware.Component.Unrelated	These common components have files and keys that are in different threats but the threats are not related to one another in that the author of the signature is not the same. It is recommended that all these entries be removed.
Virus.Parite.B	Virus Parite.B will remain in memory after executed, and infecting every SCR and PE file on every drive and network share.
Backdoor.ProRat	Backdoor.ProRat is a remote administrative trojan. It allows an attacker to take full control of a compromised computer. It also logs all keystrokes to a text file which can be accessed by the attacker. It also hides itself from task manager and process monitors.

Attention! The following threat categories were identified:

Threat Category	Description
	A malicious backdoor trojan that runs in the background and allows remote access to the compromised system
	A virus capable to modify other files by infecting, prepending, or overwriting them them with its own body

File System Modifications

The following files were created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%Windir%\ktd32.atm	88,465 bytes	MD5: 0xB28EF2D3E37B78915417DDAB0789C17D SHA-1: 0xDCACBB3E3E15456025C2ADC302911C9ACD6D27A9	(not available)
2	%Windir%\services.exe %Windir%\system\sservice.exe %System%\fservice.exe %System%\incom.exe	351,277 bytes	MD5: 0xB36E42A24BBC30C3DF234CD2915B2FE2 SHA-1: 0xA79FA344E9514609AD19DE8599E7EE4E1134EFF0	Backdoor.Prorat [Symantec] Backdoor.Win32.Prorat.b [Kaspersky Lab] BackDoor-AVW [McAfee] BKDR_PRORAT.19 [Trend Micro] Troj/Prorat-L [Sophos] Backdoor:Win32/Prorat.N [Microsoft] Win32.SuspectCrc [Ikarus] Win-Trojan/Prorat.351276.T [AhnLab]
3	%Windir%\svchost.exe	36,352 bytes	MD5: 0x9E3C13B6556D5636B745D3E466D47467 SHA-1: 0x2AC1C19E268C49BC508F83FE3D20F495DEB3E538	W32.Jeefo [Symantec] Virus.Win32.Hidrag.a [Kaspersky Lab] W32/Jeefo [McAfee] TROJ_FLOOD.AF [Trend Micro] W32/Jeefo-A [Sophos] Trojan:Win32/Jeefo.A [Microsoft] Virus.Win32.Hidrag [Ikarus] Win32/Hidrag [AhnLab]
4	%System%\incom_.exe	3,162,880 bytes	MD5: 0xD150258D0882CC5BD85EA881FE5D4CCE SHA-1: 0x3845F8CCB6D16D972603763CCD5A1D046C1BAE93	Backdoor.Prorat [Symantec] Generic.dc [McAfee] Mal/Behav-105 [Sophos] VirTool.Win32.AntiDote [Ikarus] Win-Trojan/Prorat.3162880 [AhnLab] packed with PE_Patch.UltraProtect [Kaspersky Lab]
5	%System%\language\English.ini	37,708 bytes	MD5: 0xB6F92705DE4CB97C5036C039CA7BA79C SHA-1: 0x52BD64A45176E09122714276949D0C2601EE5E2F	(not available)
6	%System%\reginv.dll	20,992 bytes	MD5: 0x904F3B552D0B762EDB4520163D12D3CF SHA-1: 0x5CCA6B60732FE12D5D0D33E2FB2EB0C9004B9A8A	Backdoor.Prorat [Symantec] BackDoor-AVW [McAfee] BKDR_PRORAT.F [Trend Micro] Troj/Prorat-L [Sophos] Backdoor:Win32/Prorat.1_9 [Microsoft] Backdoor.Win32.Prorat [Ikarus] Win-Trojan/Prorat_v19.20992 [AhnLab]
7	[file and pathname of the sample #1]	3,518,596 bytes	MD5: 0x2AA563EBE7C5856140962DB0909863AD SHA-1: 0xD22D50B44731630A0F475672712D0A064B5EB39F	Backdoor.Prorat [Symantec] Downloader-MP [McAfee] BKDR_PRORAT.A [Trend Micro] Troj/Prorat-J [Sophos] Backdoor.Win32.Prorat [Ikarus] Win-Trojan/Prorat.367377 [AhnLab]
8	%System%\winkey.dll	16,896 bytes	MD5: 0xD910659CCA6A1650C10FF263C8A10FE7 SHA-1: 0xD38DBCCB50B63430A51D8F6DF2A6C4D23677CFF0	Backdoor.Prorat [Symantec] BackDoor-AVW [McAfee] BKDR_PRORAT.AB [Trend Micro] Troj/Prorat-H [Sophos] Backdoor:Win32/Prorat.1_9 [Microsoft] Backdoor.Win32.Prorat [Ikarus] Win-Trojan/Prorat.13312 [AhnLab]

Notes:

%Windir% is a variable that refers to the Windows installation folder. By default, this is C:\Windows or C:\Winnt.
%System% is a variable that refers to the System folder. By default, this is C:\Windows\System (Windows 95/98/Me), C:\Winnt\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP).

The following directories were created:

%System%\Download
%System%\Images
%System%\language

Memory Modifications

There were new processes created in the system:

Process Name	Process Filename	Main Module Size
svchost.exe	%Windir%\svchost.exe	53,248 bytes
incom_.exe	%System%\incom_.exe	4,096 bytes
sservice.exe	%Windir%\system\sservice.exe	2,068,480 bytes
fservice.exe	%System%\fservice.exe	2,068,480 bytes
incom.exe	%System%\incom.exe	2,068,480 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	53,248 bytes
services.exe	%Windir%\services.exe	2,068,480 bytes

The following modules were loaded into the address space of other process(es):

Module Name	Module Filename	Address Space Details
reginv.dll	%System%\reginv.dll	Process name: dllhost.exe Process filename: %System%\dllhost.exe Address space: 0x17B0000 - 0x17B8000
reginv.dll	%System%\reginv.dll	Process name: incom_.exe Process filename: %System%\incom_.exe Address space: 0x20C0000 - 0x20C8000
winkey.dll	%System%\winkey.dll	Process name: incom_.exe Process filename: %System%\incom_.exe Address space: 0x3070000 - 0x307B000
winkey.dll	%System%\winkey.dll	Process name: services.exe Process filename: %Windir%\services.exe Address space: 0xA90000 - 0xA9B000
reginv.dll	%System%\reginv.dll	Process name: services.exe Process filename: %Windir%\services.exe Address space: 0xAD0000 - 0xAD8000
reginv.dll	%System%\reginv.dll	Process name: VMwareUser.exe Process filename: %ProgramFiles%\vmware\vmware tools\vmwareuser.exe Address space: 0x9A0000 - 0x9A8000

Notes:

%ProgramFiles% is a variable that refers to the Program Files folder. A typical path is C:\Program Files.

There was a new service created in the system:

Service Name	Display Name	Status	Service Filename
PowerManager	Power Manager	"Running"	%Windir%\svchost.exe

The following system services were modified:

Service Name	Display Name	New Status	Service Filename
ALG	Application Layer Gateway Service	"Stopped"	%System%\alg.exe
SharedAccess	Windows Firewall/Internet Connection Sharing (ICS)	"Stopped"	%System%\svchost.exe -k netsvcs

Registry Modifications

The following Registry Keys were created:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{5Y99AE78-58TT-11dW-BE53-Y67078979Y}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\Run
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER\0000\Control
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager\Security
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager\Enum
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER\0000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER\0000\Control
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager\Security
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager\Enum
HKEY_CURRENT_USER\Software\Microsoft\Windows NT Script Host
HKEY_CURRENT_USER\Software\Microsoft\Windows NT Script Host\Microsoft DxDiag
HKEY_CURRENT_USER\Software\Microsoft\Windows NT Script Host\Microsoft DxDiag\WinSettings
HKEY_CURRENT_USER\Software\P?O Group
HKEY_CURRENT_USER\Software\P?O Group\ProMessenger
HKEY_CURRENT_USER\Software\P?O Group\ProRat V1.9 (S.Edition)
HKEY_CURRENT_USER\Software\P?O Group\ProRat V1.9 (S.Edition)\Ip_Adrs

The newly created Registry Values are:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{5Y99AE78-58TT-11dW-BE53-Y67078979Y}]

StubPath = "%Windir%\system\sservice.exe"

so that sservice.exe runs every time Windows starts

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\Run]

DirectX For Microsoft? Windows = "%System%\fservice.exe"

so that fservice.exe runs every time Windows starts

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER\0000\Control]

*NewlyCreated* = 0x00000000
ActiveService = "PowerManager"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER\0000]

Service = "PowerManager"
Legacy = 0x00000001
ConfigFlags = 0x00000000
Class = "LegacyDriver"
ClassGUID = "{8ECC055D-047F-11D1-A537-0000F8753ED1}"
DeviceDesc = "Power Manager"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POWERMANAGER]

NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager\Enum]

0 = "Root\LEGACY_POWERMANAGER\0000"
Count = 0x00000001
NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager\Security]

Security = 01 00 14 80 90 00 00 00 9C 00 00 00 14 00 00 00 30 00 00 00 02 00 1C 00 01 00 00 00 02 80 14 00 FF 01 0F 00 01 01 00 00 00 00 00 01 00 00 00 00 02 00 60 00 04 00 00 00 00 00 14 00 FD 01 02 00 01 01 00 00 00 00 00 05 12 00 00 00 00 00 18 00 FF 01 0F 0

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PowerManager]

Type = 0x00000010
Start = 0x00000002
ErrorControl = 0x00000000
ImagePath = "%Windir%\svchost.exe"
DisplayName = "Power Manager"
ObjectName = "LocalSystem"
Description = "Manages the power save features of the computer."

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER\0000\Control]

*NewlyCreated* = 0x00000000
ActiveService = "PowerManager"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER\0000]

Service = "PowerManager"
Legacy = 0x00000001
ConfigFlags = 0x00000000
Class = "LegacyDriver"
ClassGUID = "{8ECC055D-047F-11D1-A537-0000F8753ED1}"
DeviceDesc = "Power Manager"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_POWERMANAGER]

NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager\Enum]

0 = "Root\LEGACY_POWERMANAGER\0000"
Count = 0x00000001
NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager\Security]

Security = 01 00 14 80 90 00 00 00 9C 00 00 00 14 00 00 00 30 00 00 00 02 00 1C 00 01 00 00 00 02 80 14 00 FF 01 0F 00 01 01 00 00 00 00 00 01 00 00 00 00 02 00 60 00 04 00 00 00 00 00 14 00 FD 01 02 00 01 01 00 00 00 00 00 05 12 00 00 00 00 00 18 00 FF 01 0F 0

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerManager]

Type = 0x00000010
Start = 0x00000002
ErrorControl = 0x00000000
ImagePath = "%Windir%\svchost.exe"
DisplayName = "Power Manager"
ObjectName = "LocalSystem"
Description = "Manages the power save features of the computer."

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT Script Host\Microsoft DxDiag\WinSettings]

Bulas = "1"
FW_KILL = "1"
XP_FW_Disable = "1"
XP_SYS_Recovery = "1"
ICQ_UIN = "`lhod627/on,hq/hogn"
ICQ_UIN2 = ""
Kurban_Ismi = "qsns`u"
Mail = "`lhod627Ainul`hm/bnl"
Online_List = ""
Port = "4001"
Sifre = "`mhc`c`"
Hata = "Welcome to prorat 2.0 Fixe1 SE"
KSil = "0"
LanNotifie = ""
Tport = "1"
ServerVersionInt = "19"

[HKEY_CURRENT_USER\Software\P?O Group\ProRat V1.9 (S.Edition)\Ip_Adrs]

Sayi = "2"
Ip2 = "127.0.0.1"

[HKEY_CURRENT_USER\Software\P?O Group\ProRat V1.9 (S.Edition)]

Genel_Sifre = "123456"
Son_Ip = "127.0.0.1"
Son_Port = "5110"
skin = "0"
LanguageId = "0"

[HKEY_CURRENT_USER\Software\P?O Group\ProMessenger]

skin = "0"

The following Registry Values were modified:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

Shell =

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ServiceCurrent]

(Default) =

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceCurrent]

(Default) =

Other details

Analysis of the file resources indicate the following possible country of origin:

Turkey

To mark the presence in the system, the following Mutex object was created:

Global\PowerManagerMutant

The following Host Name was requested from a host database:

0.0.0.0

There were application-defined hook procedures installed into the hook chain (e.g. to monitor keystrokes). The installed hooks are handled by the following modules:

%System%\winkey.dll

the hook is handled by its export "Kisses_To_Trojanhunter()"

%System%\reginv.dll

the hook is handled by its export "HookProc()"

All content ("Information") contained in this report is the copyrighted work of Threat Expert Ltd and its associated companies ("ThreatExpert") and may not be copied without the express permission of ThreatExpert.

The Information is provided on an "as is" basis. ThreatExpert disclaims all warranties, whether express or implied, to the maximum extent permitted by law, including the implied warranties that the Information is merchantable, of satisfactory quality, accurate, fit for a particular purpose or need, or non-infringing, unless such implied warranties are legally incapable of exclusion. Further, ThreatExpert does not warrant or make any representations regarding the use or the results of the use of the Information in terms of their correctness, accuracy, reliability, or otherwise.