arrow_back
search
close

BKDR_DYRE.YYSPG

November 22, 2015
 Analysis by: David John Agni
 ALIASES:

PWS:Win32/Dyzap.A (Microsoft), W32/Dyreza.LL!tr (Fortinet)

 PLATFORM:

Windows

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

  • Threat Type: Backdoor

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel:

Downloaded from the Internet, Dropped by other malware

This backdoor may be downloaded by other malware/grayware/spyware from remote sites.

It uses the Windows Task Scheduler to add a scheduled task that executes the copies it drops.

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

It deletes itself after execution.

  TECHNICAL DETAILS

File Size:

138752 bytes

File Type:

DLL

Memory Resident:

Yes

Initial Samples Received Date:

13 Nov 2015

Payload:

Steals information

Arrival Details

This backdoor may be downloaded by other malware/grayware/spyware from remote sites.

Installation

This backdoor uses the Windows Task Scheduler to add a scheduled task that executes the copies it drops.

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

  • Global\u1nyj3rt20

It injects codes into the following process(es):

  • firefox.exe
  • iexplore.exe
  • Microsoft Edge
  • chrome.exe

Backdoor Routine

This backdoor executes the following commands from a remote malicious user:

  • Receive configuration(web injects/MitB)
  • Receive New connections
  • Create Backdoor connection
  • Download Module (vnc32, tv32, wg32, pn32, rdpp32, pdf32)
  • Reboot Computer
  • Create User Admin Account
  • Wipe MBR, Drives C and D
  • Browser Snapshot
  • Download file and execute
  • Create scheduled task to execute a file every minute

It connects to the following URL(s) to send and receive commands from a remote malicious user:

  • {BLOCKED}.{BLOCKED}.116.240:443
  • {BLOCKED}.{BLOCKED}.49.163:443
  • {BLOCKED}.{BLOCKED}.49.186:443
  • {BLOCKED}.{BLOCKED}.247.133:4443
  • {BLOCKED}.{BLOCKED}.21.168:4443
  • {BLOCKED}.{BLOCKED}.22.227:443
  • {BLOCKED}.{BLOCKED}.75.159:4443
  • {BLOCKED}.{BLOCKED}.2.2:443
  • {BLOCKED}.{BLOCKED}.169.172:443
  • {BLOCKED}.{BLOCKED}.145.111:4443
  • {BLOCKED}.{BLOCKED}.145.121:443
  • {BLOCKED}.{BLOCKED}.214.50:443
  • {BLOCKED}.{BLOCKED}.19.156:443
  • {BLOCKED}.{BLOCKED}.196.26:443
  • {BLOCKED}.{BLOCKED}.97.238:4443
  • {BLOCKED}.{BLOCKED}.54.6:4443
  • {BLOCKED}.{BLOCKED}.55.101:4443
  • {BLOCKED}.{BLOCKED}.12.19:4443
  • {BLOCKED}.{BLOCKED}.15.194:4443
  • {BLOCKED}.{BLOCKED}.67.128:443
  • {BLOCKED}.{BLOCKED}.203.9:443
  • {BLOCKED}.{BLOCKED}.243.172:4443
  • {BLOCKED}.{BLOCKED}.173.18:4443
  • {BLOCKED}.{BLOCKED}.100.179:443
  • {BLOCKED}.{BLOCKED}.85.128:4443
  • {BLOCKED}.{BLOCKED}.51.81:443
  • {BLOCKED}.{BLOCKED}.53.233:4443
  • {BLOCKED}.{BLOCKED}.94.197:4443
  • {BLOCKED}.{BLOCKED}.65.16:4443
  • {BLOCKED}.{BLOCKED}.96.68:443
  • {BLOCKED}.{BLOCKED}.195.53:4443
  • {BLOCKED}.{BLOCKED}.205.69:443
  • {BLOCKED}.{BLOCKED}.145.138:4443
  • {BLOCKED}.{BLOCKED}.50.85:443
  • {BLOCKED}.{BLOCKED}.191.206:4443
  • {BLOCKED}.{BLOCKED}.204.74:443
  • {BLOCKED}.{BLOCKED}.2.228:443
  • {BLOCKED}.{BLOCKED}.17.76:4443
  • {BLOCKED}.{BLOCKED}.27.162:4443
  • {BLOCKED}.{BLOCKED}.39.126:443
  • {BLOCKED}.{BLOCKED}.207.29:4443
  • {BLOCKED}.{BLOCKED}.224.143:4443
  • {BLOCKED}.{BLOCKED}.194.108:4443
  • {BLOCKED}.{BLOCKED}.216.5:4443
  • {BLOCKED}.{BLOCKED}.106.26:443
  • {BLOCKED}.{BLOCKED}.115.117:443
  • {BLOCKED}.{BLOCKED}.19.13:443
  • {BLOCKED}.{BLOCKED}.224.118:4443
  • {BLOCKED}.{BLOCKED}.186.146:4443
  • {BLOCKED}.{BLOCKED}.44.38:4443

Information Theft

This backdoor s configuration file contains the following information:

  • List of strings related to banking/bitcoin
  • Proxy address for the Man-in-the-middle attack
  • List of new C&C server

It gathers the following data:

  • Host Name
  • Public IP Address
  • Computer Name
  • OS Version
  • OS Platform
  • User Accounts
  • System Info(CPU, Memory, No. of Processors)
  • Installed programs
  • Services

Other Details

This backdoor connects to the following URL(s) to check for an Internet connection:

  • google.com
  • microsoft.com

It connects to the following URL(s) to get the affected system's IP address:

  • http://icanhazip.com

It does the following:

  • Monitors the following browsers:
    • chrome.exe
    • firefox.exe
    • iexplore.exe
    • microsoftedge
  • Connects to the following STUN (Session Traversal Utilities for NAT) server in order to determine the public IP address of the compromised computer:
    • stun1.voiceeclipse.net
    • stun.callwithus.com
    • stun.sipgate.net
    • stun.ekiga.net
    • stun.internetcalls.com
    • stun.noc.ams-ix.net
    • stun.voip.aebc.com
    • stun.voipbuster.com
    • stun.voxgratia.org
    • stun.ipshka.com
    • stun.faktortel.com.au
    • stun.iptel.org
    • stun.voipstunt.com
    • 203.183.172.196:3478
    • s1.taraba.net
    • stun.l.google.com:19302
    • stun1.l.google.com:19302
    • stun2.l.google.com:19302
    • stun3.l.google.com:19302
    • stun4.l.google.com:19302
    • stun.schlund.de
    • stun.rixtelecom.se
    • stun.voiparound.com
    • numb.viagenie.ca
    • stun.stunprotocol.org
    • stun.services.mozilla.com
    • stun.2talk.co.nz
  • Stop the following services:
    • wscsvc
    • MpsSvc
    • WinDefend

It deletes itself after execution.

  SOLUTION

Minimum Scan Engine:

9.8

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

Note that not all files, folders, and registry keys and entries are installed on your computer during this malware's/spyware's/grayware's execution. This may be due to incomplete installation or other operating system conditions. If you do not find the same files/folders/registry information, please proceed to the next step.

Step 3

Restart in Safe Mode

[ Learn More ]

Step 4

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

Step 5

Delete the Scheduled Tasks added by this malware/grayware

[ Learn More ]

To delete the added Scheduled Task file:

For Windows 2000, Windows XP, and Windows Server 2003:

  1. Open the Windows Scheduled Tasks. To do this, click Start>Programs>Accessories>System Tools>Scheduled Tasks.
  2. Double-click on a .JOB file.
  3. Check if the malware path and file name exists in the .JOB file. To do this, check the value in the Run field.
  4. If found, select the .JOB file then press SHIFT+DELETE to permanently delete the file.
  5. Repeat the steps above for the remaining .JOB files.

For Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows 8.1, and Windows Server 2012:

  1. Open the Windows Task Scheduler. To do this:
    • On Windows Vista, Windows 7, and Windows Server 2008, click Start, type taskschd.msc in the Search input field, then press Enter.
    • On Windows 8, Windows 8.1, and Windows Server 2012, right-click on the lower left corner of the screen, click Run, type taskschd.msc, then press Enter.
  2. In the left panel of the Task Scheduler Window, click Task Scheduler Library.
  3. In the upper-middle panel, click a Task.
  4. In the lower middle panel, click the Actions tab
  5. Check if the malware path and file name exists in the task. To do this, check the value in the Details column under the Actions tab.
  6. If found, select the task and press DELETE and click Yes to delete the task.
  7. Repeat the steps above for the remaining tasks.

Step 6

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