TROJ_SIREFEF.ZV

 Analysis by: Mark Joseph Manahan

 ALIASES:

Trojan:Win32/Sirefef.P (Microsoft), Backdoor.Trojan (Symantec)

 PLATFORM:

Windows 2000, Windows XP, Windows Server 2003

 OVERALL RISK RATING:
 DAMAGE POTENTIAL:
 DISTRIBUTION POTENTIAL:
 REPORTED INFECTION:

  • Threat Type: Trojan

  • Destructiveness: No

  • Encrypted:

  • In the wild: Yes

  OVERVIEW

This Trojan arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

  TECHNICAL DETAILS

File Size:

190,464 bytes

File Type:

EXE

Memory Resident:

Yes

Initial Samples Received Date:

17 Aug 2012

Arrival Details

This Trojan arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

Installation

This Trojan creates the following folders:

  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}
  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\U
  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\L
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\U
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\L

(Note: %Application Data% is the current user's Application Data folder, which is usually C:\Windows\Profiles\{user name}\Application Data on Windows 98 and ME, C:\WINNT\Profiles\{user name}\Application Data on Windows NT, and C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000, XP, and Server 2003.. %Windows% is the Windows folder, which is usually C:\Windows or C:\WINNT.)

Autostart Technique

This Trojan creates the following registry entries to enable automatic execution of dropped component at every system startup:

HKEY_CURRENT_USER\Software\Classes\
CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}
ThreadingModel = "Both"

HKEY_CURRENT_USER\Software\Classes\
CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}
@ = "%Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\n."

Other System Modifications

This Trojan modifies the following registry entries:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\
CLSID\{F3130CDB-AA52-4C3A-AB32-85FFC23AF9C1}\InprocServer32
@ = "\.\globalroot\systemroot\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\n."

(Note: The default value data of the said registry entry is "%System%\wbem\wbemess.dll".)

HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\
InProcServer32
@ = "%Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\n."

(Note: The default value data of the said registry entry is %System%\wbem\wbemess.dll.)

HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\
InProcServer32
ThreadingModel = "Both"

(Note: The default value data of the said registry entry is "Apartment".)

Dropping Routine

This Trojan drops the following files:

  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\@
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\n
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\U\00000001.@
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\U\80000000.@
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\U\800000cb.@
  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\@
  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\n

(Note: %Windows% is the Windows folder, which is usually C:\Windows or C:\WINNT.. %Application Data% is the current user's Application Data folder, which is usually C:\Windows\Profiles\{user name}\Application Data on Windows 98 and ME, C:\WINNT\Profiles\{user name}\Application Data on Windows NT, and C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000, XP, and Server 2003.)

  SOLUTION

Minimum Scan Engine:

9.200

FIRST VSAPI PATTERN FILE:

9.330.06

FIRST VSAPI PATTERN DATE:

18 Aug 2012

VSAPI OPR PATTERN File:

9.331.00

VSAPI OPR PATTERN Date:

18 Aug 2012

Step 1

For Windows XP and Windows Server 2003 users, before doing any scans, please make sure you disable System Restore to allow full scanning of your computer.

Step 2

Restart in Safe Mode

[ Learn More ]

Step 3

Delete this registry key

[ Learn More ]

Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this step only if you know how or you can ask assistance from your system administrator. Else, check this Microsoft article first before modifying your computer's registry.

  • In HKEY_CURRENT_USER\Software\Classes\clsid
    • {42aedc87-2188-41fd-b9a3-0c966feabec1}

Step 4

Restore this modified registry value

[ Learn More ]

Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this only if you know how to or you can seek your system administrator’s help. You may also check out this Microsoft article first before modifying your computer's registry.

  • In HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32
    • From: @ = "%Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}\n."
      To: @ = %System%\wbem\wbemess.dll
  • In HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32
    • From: ThreadingModel = "Apartment"
      To: ThreadingModel = "Both"
  • In HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F3130CDB-AA52-4C3A-AB32-85FFC23AF9C1}\InprocServer32
    • From: @ = "\\.\globalroot\systemroot\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}\n."
      To: @ = "%System%\wbem\wbemess.dll"

Step 5

Search and delete these folders

[ Learn More ]
Please make sure you check the Search Hidden Files and Folders checkbox in the More advanced options option to include all hidden folders in the search result.
  • %Application Data%\{082f346d-1afd-ef95-7a41-5848b36bed23}
  • %Windows%\Installer\{082f346d-1afd-ef95-7a41-5848b36bed23}

Step 6

Restart in normal mode and scan your computer with your Trend Micro product for files detected as TROJ_SIREFEF.ZV. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check this Knowledge Base page for more information.


Did this description help? Tell us how we did.