Loading Joe Sandbox Report ...

Edit tour

Windows Analysis Report
file.exe

Overview

General Information

Sample Name:file.exe
Analysis ID:715150
MD5:a3b774ed5023f56970eea0668ae65703
SHA1:3aebfec7980d1db1edbeccbb29044ea677be304b
SHA256:f4f6bcce8531ffa055776e57b0f650b7f87049808e3b29d65fab79ec841ed81c
Tags:exe
Infos:

Detection

Nymaim
Score:96
Range:0 - 100
Whitelisted:false
Confidence:100%

Signatures

Multi AV Scanner detection for submitted file
Malicious sample detected (through community Yara rule)
Yara detected Nymaim
Antivirus detection for URL or domain
Multi AV Scanner detection for dropped file
Binary is likely a compiled AutoIt script file
Machine Learning detection for sample
May check the online IP address of the machine
C2 URLs / IPs found in malware configuration
Uses 32bit PE files
Queries the volume information (name, serial number etc) of a device
Yara signature match
One or more processes crash
May sleep (evasive loops) to hinder dynamic analysis
Internet Provider seen in connection with other malware
Sample execution stops while process was sleeping (likely an evasion)
Found dropped PE file which has not been started or loaded
PE file contains executable resources (Code or Archives)
IP address seen in connection with other malware
Downloads executable code via HTTP
Enables debug privileges
Creates a DirectInput object (often for capturing keystrokes)
Drops files with a non-matching file extension (content does not match file extension)
Sample file is different than original file name gathered from version info
Drops PE files
Checks if the current process is being debugged
Binary contains a suspicious time stamp
Uses taskkill to terminate processes
Launches processes in debugging mode, may be used to hinder debugging
Dropped file seen in connection with other malware
Creates a process in suspended mode (likely to inject code)

Classification

  • System is w10x64
  • file.exe (PID: 5464 cmdline: C:\Users\user\Desktop\file.exe MD5: A3B774ED5023F56970EEA0668AE65703)
    • WerFault.exe (PID: 5160 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 528 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 5176 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 708 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 3332 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 716 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 2884 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 724 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 3756 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 776 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 5704 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 896 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 5836 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 908 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 5936 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 1156 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • WerFault.exe (PID: 5312 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 1228 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • cmd.exe (PID: 5996 cmdline: C:\Windows\System32\cmd.exe" /c start /I "" "C:\Users\user~1\AppData\Local\Temp\du2kVBqiTxfv\Cleaner.exe MD5: F3BDBE3BB6F734E357235F4D5898582D)
      • conhost.exe (PID: 3348 cmdline: C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 MD5: EA777DEEA782E8B4D7C7C33BBF8A4496)
      • Cleaner.exe (PID: 2380 cmdline: "C:\Users\user~1\AppData\Local\Temp\du2kVBqiTxfv\Cleaner.exe" MD5: 04514BD4962F7D60679434E0EBE49184)
        • WerFault.exe (PID: 5524 cmdline: C:\Windows\system32\WerFault.exe -u -p 2380 -s 1576 MD5: 2AFFE478D86272288BBEF5A00BBEF6A0)
        • WerFault.exe (PID: 5684 cmdline: C:\Windows\system32\WerFault.exe -u -p 2380 -s 1576 MD5: 2AFFE478D86272288BBEF5A00BBEF6A0)
    • WerFault.exe (PID: 4652 cmdline: C:\Windows\SysWOW64\WerFault.exe -u -p 5464 -s 1292 MD5: 9E2B8ACAD48ECCA55C0230D63623661B)
    • cmd.exe (PID: 1436 cmdline: "C:\Windows\System32\cmd.exe" /c taskkill /im "file.exe" /f & erase "C:\Users\user\Desktop\file.exe" & exit MD5: F3BDBE3BB6F734E357235F4D5898582D)
      • conhost.exe (PID: 604 cmdline: C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 MD5: EA777DEEA782E8B4D7C7C33BBF8A4496)
      • taskkill.exe (PID: 2888 cmdline: taskkill /im "file.exe" /f MD5: 15E2E0ACD891510C6268CB8899F2A1A1)
  • cleanup
{"C2 addresses": ["208.67.104.97", "85.31.46.167"]}
SourceRuleDescriptionAuthorStrings
00000000.00000000.423202429.0000000000400000.00000040.00000001.01000000.00000003.sdmpJoeSecurity_NymaimYara detected NymaimJoe Security
    00000000.00000000.436811597.00000000008F9000.00000040.00000020.00020000.00000000.sdmpWindows_Trojan_RedLineStealer_ed346e4cunknownunknown
    • 0xaf0:$a: 55 8B EC 8B 45 14 56 57 8B 7D 08 33 F6 89 47 0C 39 75 10 76 15 8B
    00000000.00000000.404054334.00000000008F9000.00000040.00000020.00020000.00000000.sdmpWindows_Trojan_RedLineStealer_ed346e4cunknownunknown
    • 0xaf0:$a: 55 8B EC 8B 45 14 56 57 8B 7D 08 33 F6 89 47 0C 39 75 10 76 15 8B
    00000000.00000000.398224905.0000000000400000.00000040.00000001.01000000.00000003.sdmpJoeSecurity_NymaimYara detected NymaimJoe Security
      00000000.00000000.429736065.0000000000400000.00000040.00000001.01000000.00000003.sdmpJoeSecurity_NymaimYara detected NymaimJoe Security
        Click to see the 60 entries
        SourceRuleDescriptionAuthorStrings
        0.0.file.exe.400000.7.raw.unpackJoeSecurity_NymaimYara detected NymaimJoe Security
          0.0.file.exe.860e67.24.unpackJoeSecurity_NymaimYara detected NymaimJoe Security
            0.0.file.exe.860e67.16.raw.unpackJoeSecurity_NymaimYara detected NymaimJoe Security
              0.0.file.exe.400000.0.unpackJoeSecurity_NymaimYara detected NymaimJoe Security
                0.0.file.exe.400000.11.raw.unpackJoeSecurity_NymaimYara detected NymaimJoe Security