WORM_PALEVO.EP

 Analysis by: kathleenno

 ALIASES:

Trojan.Gen (Symantec); VirTool:Win32/VBInject.gen!ET (Microsoft); Trojan.Win32.VB.aonf (Kaspersky); Generic.dx!vpv (Mcafee); Mal/Generic-L (Sophos)

 PLATFORM:

Windows 2000, Windows XP, Windows Server 2003

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

  • Threat Type: Worm

  • Destructiveness: No

  • Encrypted: No

  • In the wild: Yes

  OVERVIEW


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

It drops copies of itself in all removable drives. It drops an AUTORUN.INF file to automatically execute the copies it drops when a user accesses the drives of an affected system.

  TECHNICAL DETAILS

File Size:

156,815 bytes

File Type:

EXE

Memory Resident:

Yes

Initial Samples Received Date:

22 Jun 2011

Arrival Details

This worm 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 worm drops the following copies of itself into the affected system:

  • %Application Data%\kvmm.exe

(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.)

It injects itself into the following processes as part of its memory residency routine:

  • explorer.exe

Autostart Technique

This worm adds the following registry entries to enable its automatic execution at every system startup:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows NT\CurrentVersion\Winlogon
Taskman = "%Application Data%\kvmm.exe"

Propagation

This worm drops copies of itself in all removable drives.

It drops an AUTORUN.INF file to automatically execute the copies it drops when a user accesses the drives of an affected system.

The said .INF file contains the following strings:

;{garbage characters}
[AUtorUN
;{garbage characters}
OPEN=sys/////////////sys.exe
;{garbage characters}
USEAuTopLAY=1
;{garbage characters}
SHELL\\\EXplore\\COMMAND=sys/\/\/\sys.exe
;{garbage characters}
SHELL\\\OPEN\\COMMAND=sys/\/\/\/\//\sys.exe
;{garbage characters}

  SOLUTION

Minimum Scan Engine:

8.900

FIRST VSAPI PATTERN FILE:

8.256.15

FIRST VSAPI PATTERN DATE:

30 Jun 2011

VSAPI OPR PATTERN File:

8.257.00

VSAPI OPR PATTERN Date:

30 Jun 2011

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

Identify and delete files detected as WORM_PALEVO.EP using either the Startup Disk or Recovery Console

[ Learn More ]

Step 3

Delete this registry value

[ 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_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
    • Taskman = "%Application Data%\kvmm.exe"

Step 4

Search and delete AUTORUN.INF files created by WORM_PALEVO.EP that contain these strings

[ Learn More ]
;{garbage characters}
[AUtorUN
;{garbage characters}
OPEN=sys/////////////sys.exe
;{garbage characters}
USEAuTopLAY=1
;{garbage characters}
SHELL\\EXplore\COMMAND=sys/\/\/\sys.exe
;{garbage characters}
SHELL\\OPEN\COMMAND=sys/\/\/\/\//\sys.exe
;{garbage characters}

Step 5

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