TROJ_ROVNIX.YPNJ

 Modified by: RonJay Kristoffer Caragay

 ALIASES:

Trojan:Win32/Peals!gfc (Microsoft); Trojan-FFDU!8D11ECC0EC68 (McAfee); Trojan.Gen.SMH (Symantec); Trojan.Win32.Cidox.amgz (Kaspersky); Trojan.Win32.Generic!BT (Sunbelt); Trojan horse Crypt3.BAUW (AVG)

 PLATFORM:

Windows

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

  • Threat Type: Trojan

  • Destructiveness: No

  • Encrypted:

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

However, as of this writing, the said sites are inaccessible. It deletes the initially executed copy of itself.

  TECHNICAL DETAILS

File Size:

576,000 bytes

File Type:

EXE

Memory Resident:

No

Initial Samples Received Date:

10 Jan 2015

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.

Other System Modifications

This Trojan adds the following registry keys:

HKEY_CLASSES_ROOT\CLSID\{CLSID}

HKEY_LOCAL_MACHINE\Software\Classes\
CLSID\{CLSID}

Other Details

This Trojan connects to the following possibly malicious URL:

  • {BLOCKED}letitbe.com

However, as of this writing, the said sites are inaccessible.

It deletes the initially executed copy of itself

  SOLUTION

Minimum Scan Engine:

9.700

FIRST VSAPI PATTERN FILE:

11.392.04

FIRST VSAPI PATTERN DATE:

05 Jan 2015

VSAPI OPR PATTERN File:

11.393.00

VSAPI OPR PATTERN Date:

05 Jan 2015

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

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

The following created files/folders/registry keys/registry entries cannot be identified by the user since there are no reference values in the created key. The only way it can be identified is by comparing the present system information with a backup. Note that the said components do not have to be deleted since it won't be harmful to the system.

 
  • In HKEY_LOCAL_MACHINE\Software\Classes\CLSID
    • {CLSID}
  • In HKEY_CLASSES_ROOT\CLSID
    • {CLSID}


Did this description help? Tell us how we did.