Analysis by: John Kevin Sanchez

ALIASES:

Ransom:MSIL/Ryzerlo.A (Microsoft), Trojan-Ransom.MSIL.Tear.cz (Kaspersky)

 PLATFORM:

Windows

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

  • Threat Type: Ransomware

  • Destructiveness: No

  • Encrypted: No

  • In the wild: Yes

  OVERVIEW

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

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

It connects to certain websites to send and receive information.

It encrypts files with specific file extensions. It encrypts files found in specific folders. It drops files as ransom note.

  TECHNICAL DETAILS

File Size: 142,336 bytes
File Type: EXE
Memory Resident: No
Initial Samples Received Date: 05 May 2017
Payload: Drops files, Connects to URLs/IPs, Encrypts files

Arrival Details

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

Other System Modifications

This Ransomware sets the system's desktop wallpaper to the following image:

  • This ransomware sets this image as wallpaper:

Download Routine

This Ransomware accesses the following websites to download files:

  • https://i.{BLOCKED}r.com/5iVZ4gf.jpg

Other Details

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

  • http://www.{BLOCKED}e.com/panel/createkeys.php
  • http://www.{BLOCKED}e.com/panel/savekey.php

Ransomware Routine

This Ransomware encrypts files with the following extensions:

  • .txt
  • .doc
  • .docx
  • .xls
  • .xlsx
  • .ppt
  • .pptx
  • .odt
  • .jpg
  • .png
  • .csv
  • .sql
  • .mdb
  • .sln
  • .php
  • .asp
  • .aspx
  • .html
  • .xml
  • .psd

It encrypts files found in the following folders:

  • %Desktop%\test

(Note: %Desktop% is the desktop folder, where it usually is C:\Documents and Settings\{user name}\Desktop in Windows 2000, Windows Server 2003, and Windows XP (32- and 64-bit); C:\Users\{user name}\Desktop in Windows Vista (32- and 64-bit), Windows 7 (32- and 64-bit), Windows 8 (32- and 64-bit), Windows 8.1 (32- and 64-bit), Windows Server 2008, and Windows Server 2012.)

It appends the following extension to the file name of the encrypted files:

  • .locked

It drops the following file(s) as ransom note:

  • %User Profile%\ransom.jpg

(Note: %User Profile% is the current user's profile folder, which is usually C:\Documents and Settings\{user name} on Windows 2000, XP, and Server 2003, or C:\Users\{user name} on Windows Vista and 7.)

  SOLUTION

Minimum Scan Engine: 9.850
FIRST VSAPI PATTERN FILE: 13.392.08
FIRST VSAPI PATTERN DATE: 08 May 2017
VSAPI OPR PATTERN File: 13.393.00
VSAPI OPR PATTERN Date: 09 May 2017

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

Search and delete these files

[ Learn More ]
There may be some files that are hidden. Please make sure you check the Search Hidden Files and Folders checkbox in the "More advanced options" option to include all hidden files and folders in the search result.  
  • %User Profile%\ransom.jpg

Step 4

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

Restore encrypted files from backup.


Did this description help? Tell us how we did.