arrow_back
search
close

TROJ_POWP.AB

October 08, 2012
 Analysis by: JessaD
 ALIASES:

TrojanDownloader:Win32/Unruy.H (Microsoft), Trojan.Win32.Powp.lea (Kaspersky), Backdoor.Trojan (Symantec))

 PLATFORM:

Windows 2000, XP, Server 2003

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

  • Threat Type: Trojan

  • Destructiveness: No

  • Encrypted: Yes

  • 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.

It steals certain information from the system and/or the user.

It connects to certain websites to send and receive information.

  TECHNICAL DETAILS

File Size:

37,892 bytes

File Type:

PE

Memory Resident:

Yes

Initial Samples Received Date:

29 Jan 2011

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 adds the following mutexes to ensure that only one of its copies runs at any one time:

  • j5o25jSFws

Information Theft

This Trojan steals the following information:

  • Windows Product ID
  • Computer Name
  • System Information

Other Details

This Trojan connects to the following website to send and receive information:

  • 83.{BLOCKED}3.{BLOCKED}9.139

It does the following:

  • Enumerates the entries in the following registry keys:
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
    It then overwrites the files referenced in these registries with copies of itself. The legitimate files are saved as {filename}{space}.exe. However, it will not replace the files if they are located in the following:
    • %System%
    • %Windows%\Fonts
  • Checks if processes with the following substrings are running in the system:
    • PXAgent
    • PXConsole
    • ad-watch
    • almon
    • alsvc
    • alusched
    • apvxdwin
    • ashdisp
    • ashmaisv
    • ashserv
    • ashwebsv
    • avcenter
    • avciman
    • avengine
    • avesvc
    • avgnt
    • avguard
    • bdagent
    • bdmcon
    • caissdt
    • cavrid
    • cavtray
    • ccapp
    • ccetvm
    • cclaw
    • ccproxy
    • ccsetmgr
    • clamtray
    • clamwin
    • counter
    • dpasnt
    • drweb
    • firewalln
    • fsguidll
    • fsm32
    • fspex
    • guardxkickoff
    • hsock
    • isafe
    • kavpf
    • kpf4gui
    • kpf4ss
    • livesrv
    • mcage
    • mcdet
    • mcshi
    • mctsk
    • mcupd
    • mcupdm
    • mcvss
    • mpeng
    • mpfag
    • mpfser
    • msascui
    • mscif
    • mskage
    • msksr
    • msmps
    • mxtask
    • navapsvc
    • nipsvc
    • njeeves
    • nod32krn
    • nod32kui
    • npfmsg2
    • npfsvice
    • nscsrvce
    • nvcoas
    • nvcsched
    • oascl
    • pavfnsvr
    • pxagent
    • pxcons
    • savadmins
    • savser
    • scfmanager
    • scfservice
    • scftray
    • sndsrvc
    • spbbcsvc
    • spidernt
    • spiderui
    • spysw
    • sunprotect
    • sunserv
    • sunthreate
    • swdoct
    • symlcsvc
    • tsanti
    • vba32ldr
    • vir.exe
    • vsmon
    • vsserv
    • webproxy
    • webroot
    • winssno
    • wmiprv
    • xcommsvr
    • zanda
    • zlcli

(Note: %Windows% is the Windows folder, which is usually C:\Windows or C:\WINNT.)

  SOLUTION

Minimum Scan Engine:

8.900

VSAPI PATTERN File:

7.798.20

VSAPI PATTERN Date:

29 Jan 2011

VSAPI PATTERN Date:

1/29/2011 12:00:00 AM

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

Scan your computer with your Trend Micro product to delete files detected as TROJ_POWP.AB. 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.

NOTES:
Note: Follow this step after restarting your computer into Safe Mode.<br> Restore the filenames of the overwritten files by removing the {space} between the {filename} and the {period}. The location of these files are found in the following registries: <ul><li>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run</li> <li>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run</li></ul>


Did this description help? Tell us how we did.