Analysis
- max time kernel
111s - max time network
136s - platform
windows10_x64 - resource
win10v20210408 - submitted
13/09/2021, 06:24
Static task
static1
Behavioral task
behavioral1
Sample
e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe
Resource
win7-en
Behavioral task
behavioral2
Sample
e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe
Resource
win10v20210408
General
- Target e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe
- Size 694KB
- Sample210913-g5224sdad6
- SHA256 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38
- MD5 646b4f01edaf1c9962396ef7288db784
- SHA1 32bdacc094c54c3b3bce39da9f43797ab503db3d
- SHA512 83e709be6db700ddab4e9825b55b36b8e7b799658299a102cf560a7a92645801c8fd8c6d58277286d6c0d6a22697514e17103dc1af564377f0bea7c84a505b3d
- MD5 SHA1 SHA512
Malware Config
Extracted
-
vidar
-
40.5
-
517
-
https://gheorghip.tumblr.com/
-
profile_id
517
Signatures
- Detected Djvu ransomware 7 IoCs
resource yara_rule behavioral2/memory/568-114-0x0000000002650000-0x000000000276B000-memory.dmp family_djvu behavioral2/memory/892-115-0x0000000000400000-0x0000000000537000-memory.dmp family_djvu behavioral2/memory/892-116-0x0000000000424141-mapping.dmp family_djvu behavioral2/memory/892-117-0x0000000000400000-0x0000000000537000-memory.dmp family_djvu behavioral2/memory/1764-122-0x0000000000424141-mapping.dmp family_djvu behavioral2/memory/1764-127-0x0000000000400000-0x0000000000537000-memory.dmp family_djvu behavioral2/memory/2584-134-0x00000000022E0000-0x000000000242A000-memory.dmp family_djvu - Djvu Ransomware
Ransomware which is a variant of the STOP family.
- Vidar Stealer 4 IoCs
resource yara_rule behavioral2/memory/2824-132-0x000000000049EC7D-mapping.dmp family_vidar behavioral2/memory/2824-131-0x0000000000400000-0x00000000004D5000-memory.dmp family_vidar behavioral2/memory/2824-135-0x0000000000400000-0x00000000004D5000-memory.dmp family_vidar behavioral2/memory/2584-134-0x00000000022E0000-0x000000000242A000-memory.dmp family_vidar - Downloads MZ/PE file
- Executes dropped EXE 8 IoCs
pid Process 2584 build2.exe 2824 build2.exe 3924 build3.exe 3940 build3.exe 1004 mstsca.exe 3140 mstsca.exe 2096 mstsca.exe 840 mstsca.exe - Loads dropped DLL 2 IoCs
pid Process 2824 build2.exe 2824 build2.exe - Modifies file permissions 1 TTPs 1 IoCs
pid Process 1252 icacls.exe - Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
- Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
- Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-1594587808-2047097707-2163810515-1000\Software\Microsoft\Windows\CurrentVersion\Run\SysHelper = "\"C:\\Users\\Admin\\AppData\\Local\\36a8cddf-4e90-4813-8a0a-58cb4357bc7b\\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe\" --AutoStart" e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe - Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
- Looks up external IP address via web service 3 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
flow ioc 5 api.2ip.ua 6 api.2ip.ua 13 api.2ip.ua - Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 568 set thread context of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 1456 set thread context of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 2584 set thread context of 2824 2584 build2.exe 74 PID 3924 set thread context of 3940 3924 build3.exe 76 PID 1004 set thread context of 3140 1004 mstsca.exe 91 PID 2096 set thread context of 840 2096 mstsca.exe 95 - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
- Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 build2.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString build2.exe - Creates scheduled task(s) 1 TTPs 2 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 3916 schtasks.exe 3304 schtasks.exe - Delays execution with timeout.exe 1 IoCs
pid Process 388 timeout.exe - Kills process with taskkill 1 IoCs
pid Process 1640 taskkill.exe -
description ioc Process Key created \REGISTRY\MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\D1EB23A46D17D68FD92564C2F1F1601764D8E349 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe Set value (data) \REGISTRY\MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\D1EB23A46D17D68FD92564C2F1F1601764D8E349\Blob = 5c000000010000000400000000080000090000000100000054000000305206082b0601050507030206082b06010505070303060a2b0601040182370a030406082b0601050507030406082b0601050507030606082b0601050507030706082b0601050507030106082b0601050507030853000000010000004300000030413022060c2b06010401b231010201050130123010060a2b0601040182373c0101030200c0301b060567810c010330123010060a2b0601040182373c0101030200c0620000000100000020000000d7a7a0fb5d7e2731d771e9484ebcdef71d5f0c3e0a2948782bc83ee0ea699ef40b000000010000001c0000005300650063007400690067006f002000280041004100410029000000140000000100000014000000a0110a233e96f107ece2af29ef82a57fd030a4b41d00000001000000100000002e0d6875874a44c820912e85e964cfdb030000000100000014000000d1eb23a46d17d68fd92564c2f1f1601764d8e349200000000100000036040000308204323082031aa003020102020101300d06092a864886f70d0101050500307b310b3009060355040613024742311b301906035504080c1247726561746572204d616e636865737465723110300e06035504070c0753616c666f7264311a3018060355040a0c11436f6d6f646f204341204c696d697465643121301f06035504030c18414141204365727469666963617465205365727669636573301e170d3034303130313030303030305a170d3238313233313233353935395a307b310b3009060355040613024742311b301906035504080c1247726561746572204d616e636865737465723110300e06035504070c0753616c666f7264311a3018060355040a0c11436f6d6f646f204341204c696d697465643121301f06035504030c1841414120436572746966696361746520536572766963657330820122300d06092a864886f70d01010105000382010f003082010a0282010100be409df46ee1ea76871c4d45448ebe46c883069dc12afe181f8ee402faf3ab5d508a16310b9a06d0c57022cd492d5463ccb66e68460b53eacb4c24c0bc724eeaf115aef4549a120ac37ab23360e2da8955f32258f3dedccfef8386a28c944f9f68f29890468427c776bfe3cc352c8b5e07646582c048b0a891f9619f762050a891c766b5eb78620356f08a1a13ea31a31ea099fd38f6f62732586f07f56bb8fb142bafb7aaccd6635f738cda0599a838a8cb17783651ace99ef4783a8dcf0fd942e2980cab2f9f0e01deef9f9949f12ddfac744d1b98b547c5e529d1f99018c7629cbe83c7267b3e8a25c7c0dd9de6356810209d8fd8ded2c3849c0d5ee82fc90203010001a381c03081bd301d0603551d0e04160414a0110a233e96f107ece2af29ef82a57fd030a4b4300e0603551d0f0101ff040403020106300f0603551d130101ff040530030101ff307b0603551d1f047430723038a036a0348632687474703a2f2f63726c2e636f6d6f646f63612e636f6d2f414141436572746966696361746553657276696365732e63726c3036a034a0328630687474703a2f2f63726c2e636f6d6f646f2e6e65742f414141436572746966696361746553657276696365732e63726c300d06092a864886f70d010105050003820101000856fc02f09be8ffa4fad67bc64480ce4fc4c5f60058cca6b6bc1449680476e8e6ee5dec020f60d68d50184f264e01e3e6b0a5eebfbc745441bffdfc12b8c74f5af48960057f60b7054af3f6f1c2bfc4b97486b62d7d6bccd2f346dd2fc6e06ac3c334032c7d96dd5ac20ea70a99c1058bab0c2ff35c3acf6c37550987de53406c58effcb6ab656e04f61bdc3ce05a15c69ed9f15948302165036cece92173ec9b03a1e037ada015188ffaba02cea72ca910132cd4e50826ab229760f8905e74d4a29a53bdf2a968e0a26ec2d76cb1a30f9ebfeb68e756f2aef2e32b383a0981b56b85d7be2ded3f1ab7b263e2f5622c82d46a004150f139839f95e93696986e e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe - Suspicious behavior: EnumeratesProcesses 12 IoCs
pid Process 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe 2824 build2.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1640 taskkill.exe - Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 568 wrote to memory of 892 568 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 68 PID 892 wrote to memory of 1252 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 69 PID 892 wrote to memory of 1252 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 69 PID 892 wrote to memory of 1252 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 69 PID 892 wrote to memory of 1456 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 70 PID 892 wrote to memory of 1456 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 70 PID 892 wrote to memory of 1456 892 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 70 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1456 wrote to memory of 1764 1456 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 72 PID 1764 wrote to memory of 2584 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 73 PID 1764 wrote to memory of 2584 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 73 PID 1764 wrote to memory of 2584 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 73 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 2584 wrote to memory of 2824 2584 build2.exe 74 PID 1764 wrote to memory of 3924 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 75 PID 1764 wrote to memory of 3924 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 75 PID 1764 wrote to memory of 3924 1764 e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe 75 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3924 wrote to memory of 3940 3924 build3.exe 76 PID 3940 wrote to memory of 3916 3940 build3.exe 77 PID 3940 wrote to memory of 3916 3940 build3.exe 77 PID 3940 wrote to memory of 3916 3940 build3.exe 77 PID 2824 wrote to memory of 752 2824 build2.exe 79 PID 2824 wrote to memory of 752 2824 build2.exe 79 PID 2824 wrote to memory of 752 2824 build2.exe 79 PID 752 wrote to memory of 1640 752 cmd.exe 81 PID 752 wrote to memory of 1640 752 cmd.exe 81 PID 752 wrote to memory of 1640 752 cmd.exe 81 PID 752 wrote to memory of 388 752 cmd.exe 82 PID 752 wrote to memory of 388 752 cmd.exe 82 PID 752 wrote to memory of 388 752 cmd.exe 82 PID 1004 wrote to memory of 3140 1004 mstsca.exe 91 PID 1004 wrote to memory of 3140 1004 mstsca.exe 91 PID 1004 wrote to memory of 3140 1004 mstsca.exe 91
Processes
-
C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:568 -
C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"2⤵
- Adds Run key to start application
- Modifies system certificate store
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:892 -
C:\Windows\SysWOW64\icacls.exeicacls "C:\Users\Admin\AppData\Local\36a8cddf-4e90-4813-8a0a-58cb4357bc7b" /deny *S-1-1-0:(OI)(CI)(DE,DC)3⤵
- Modifies file permissions
PID:1252
-
-
C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe" --Admin IsNotAutoStart IsNotTask3⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1456 -
C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe"C:\Users\Admin\AppData\Local\Temp\e473380efef224e3acb1a61d9c7dd49cd9c00a7dba8bef96cc376ae891da8e38.exe" --Admin IsNotAutoStart IsNotTask4⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1764 -
C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build2.exe"C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build2.exe"5⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2584 -
C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build2.exe"C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build2.exe"6⤵
- Executes dropped EXE
- Loads dropped DLL
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2824 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c taskkill /im build2.exe /f & timeout /t 6 & del /f /q "C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build2.exe" & del C:\ProgramData\*.dll & exit7⤵
- Suspicious use of WriteProcessMemory
PID:752 -
C:\Windows\SysWOW64\taskkill.exetaskkill /im build2.exe /f8⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:1640
-
-
C:\Windows\SysWOW64\timeout.exetimeout /t 68⤵
- Delays execution with timeout.exe
PID:388
-
-
-
-
-
C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build3.exe"C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build3.exe"5⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3924 -
C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build3.exe"C:\Users\Admin\AppData\Local\5f62753c-38d1-4f04-819a-f3e60f87451a\build3.exe"6⤵
- Executes dropped EXE
- Suspicious use of WriteProcessMemory
PID:3940 -
C:\Windows\SysWOW64\schtasks.exe/C /create /F /sc minute /mo 1 /tn "Azure-Update-Task" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe"7⤵
- Creates scheduled task(s)
PID:3916
-
-
-
-
-
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exeC:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe1⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1004 -
C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exeC:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe2⤵
- Executes dropped EXE
PID:3140 -
C:\Windows\SysWOW64\schtasks.exe/C /create /F /sc minute /mo 1 /tn "Azure-Update-Task" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe"3⤵
- Creates scheduled task(s)
PID:3304
-
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exeC:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe1⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
PID:2096 -
C:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exeC:\Users\Admin\AppData\Roaming\Microsoft\Network\mstsca.exe2⤵
- Executes dropped EXE
PID:840
-