Analysis by: Rika Joi Gregorio

ALIASES:

VirTool:Win32/VBInject.gen!BW(Microsoft), Win32/AutoRun.KS worm(Eset)

 PLATFORM:

Windows 2000, Windows Server 2003, Windows XP (32-bit, 64-bit), Windows Vista (32-bit, 64-bit), Windows 7 (32-bit, 64-bit)

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

  • Threat Type: Worm

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel: Downloaded from the Internet, Dropped by other malware, Propagates via flashdrives

This worm arrives by connecting affected removable drives to a system. It 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 an AUTORUN.INF file to automatically execute the copies it drops when a user accesses the drives of an affected system.

It executes commands from a remote malicious user, effectively compromising the affected system.

It performs denial of service (DoS) attacks on affected systems using specific flooding method(s).

  TECHNICAL DETAILS

File Size: 90,112 bytes
File Type: EXE
Memory Resident: Yes
Initial Samples Received Date: 31 Oct 2013
Payload: Connects to URLs/IPs, Compromises system security

Arrival Details

This worm arrives by connecting affected removable drives to a system.

It 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 files:

  • {Drive Letter}:\Feast\Ival\desktOp.Ini
  • %System Root%\Feast\Ival\desktOp.Ini

(Note: %System Root% is the root folder, which is usually C:\. It is also where the operating system is located.)

It drops the following copies of itself into the affected system:

  • %System Root%\Feast\Ival\Feast.exe

(Note: %System Root% is the root folder, which is usually C:\. It is also where the operating system is located.)

It creates the following folders:

  • %System Root%\Feast
  • %System Root%\Feast\Ival

(Note: %System Root% is the root folder, which is usually C:\. It is also where the operating system is located.)

It adds the following mutexes to ensure that only one of its copies runs at any one time:

  • Feast_v_1

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\
Active Setup\Installed Components\{random}
StubPath = "%System Root%\Feast\Ival\Feast.exe"

Other System Modifications

This worm adds the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Active Setup\Installed Components\{random}

Propagation

This worm creates the following folders in all removable drives:

  • {Drive Letter}:\Feast
  • {Drive Letter}:\Feast\Ival

It drops the following copy(ies) of itself in all removable drives:

  • {Drive Letter}:\Feast\Ival\Feast.exe

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:

[autorun]
open=Feast\Ival\Feast.exe


;wenta mal ahlak yabnel mekaka lol ma2sodaksh enta ya zaky yalla kol sana wenta tayebjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj.
action=Open folder to view files
shell\open=Open
shell\open\command=Feast\Ival\Feast.exe
shell\open\default=1

Backdoor Routine

This worm connects to any of the following IRC server(s):

  • {BLOCKED}t.{BLOCKED}rk.biz
  • {BLOCKED}t.{BLOCKED}ils.net
  • {BLOCKED}t.{BLOCKED}c.cz

It executes the following commands from a remote malicious user:

  • Download and execute files
  • Perform flooding attacks

Denial of Service (DoS) Attack

This worm performs denial of service (DoS) attacks on affected systems using the following flooding method(s):

  • UDP Flood
  • SYN Flood

Other Details

This worm uses the following credentials when accessing its IRC server:

  • PASS Virus
  • NICK VirUs-jxilocow
  • USER VirUs "" "efo" : 2,1 4IaM 7MAD 7SO FUCK OFF
  • JOIN #Feast# Virus

NOTES:

This worm sends message to its server once successfully propagate through removable drives with the following format:

  • PRIVMSG #Feast.usb# :0,1 ViroOo Own3d 0USB Driver 4 {Drive Letter}

It does not have rootkit capabilities.

It does not exploit any vulnerability.

  SOLUTION

Minimum Scan Engine: 9.300
FIRST VSAPI PATTERN FILE: 10.392.08
FIRST VSAPI PATTERN DATE: 06 Nov 2013
VSAPI OPR PATTERN File: 10.393.00
VSAPI OPR PATTERN Date: 06 Nov 2013

Step 1

Before doing any scans, Windows XP, Windows Vista, and Windows 7 users must disable System Restore to allow full scanning of their computers.

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_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components
    • {random}

Step 4

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.
  • %System Root%\Feast
  • {Drive Letter}:\Feast

Step 5

Search and delete AUTORUN.INF files created by WORM_HAMWEQ.NBD that contain these strings

[ Learn More ]
[autorun]
open=Feast\Ival\Feast.exe


;wenta mal ahlak yabnel mekaka lol ma2sodaksh enta ya zaky yalla kol sana wenta tayebjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj.
action=Open folder to view files
shell\open=Open
shell\open\command=Feast\Ival\Feast.exe
shell\open\default=1

Step 6

Restart in normal mode and scan your computer with your Trend Micro product for files detected as WORM_HAMWEQ.NBD. 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.