Analysis
- max time kernel
149s - max time network
149s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
28/03/2024, 01:38
Behavioral task
behavioral1
Sample
69c1ec6b75fa73e29475e7968ca18074.exe
Resource
win7-20240221-en
windows7-x64
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
69c1ec6b75fa73e29475e7968ca18074.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
5 signatures
150 seconds
General
- Target 69c1ec6b75fa73e29475e7968ca18074.exe
- Size 83KB
- Sample240328-b2r5vaad68
- SHA256 874ae352d63653a246680ca1d07a853702185c0dc15a756ae04aebca81f165af
- MD5 69c1ec6b75fa73e29475e7968ca18074
- SHA1 4d09c95849535110b760fae51d78522939a22a76
- SHA512 8641f7c15936633f3925186fe7402ca80bfba1298bfcb4bbee22158e986c4ecbb71824ecbf50f2459a9f4b333a1b118d489ace82d498683d5d3bcad48e36fdfb
- SSDEEP 1536:055u555555555pmgSeGDjtQhnwmmB0ybMqqU+2bbbAV2/S2mr3IdE8mne0Avu5r5:mMSjOnrmBTMqqDL2/mr3IdE8we0Avu5l
- MD5 SHA1 SHA512 SSDEEP
Score
6/10
Malware Config
Signatures
- Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-275798769-4264537674-1142822080-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\hyiechjzghm = "C:\\Users\\Admin\\AppData\\Local\\Temp\\69c1ec6b75fa73e29475e7968ca18074.exe" 69c1ec6b75fa73e29475e7968ca18074.exe - Enumerates connected drives 3 TTPs 23 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\G: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\H: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\I: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\P: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\A: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\B: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\Z: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\Q: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\R: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\N: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\O: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\S: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\T: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\U: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\W: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\E: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\L: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\X: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\M: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\V: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\Y: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\J: 69c1ec6b75fa73e29475e7968ca18074.exe File opened (read-only) \??\K: 69c1ec6b75fa73e29475e7968ca18074.exe - Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 69c1ec6b75fa73e29475e7968ca18074.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier 69c1ec6b75fa73e29475e7968ca18074.exe Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 69c1ec6b75fa73e29475e7968ca18074.exe - Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4160 69c1ec6b75fa73e29475e7968ca18074.exe 4160 69c1ec6b75fa73e29475e7968ca18074.exe 4160 69c1ec6b75fa73e29475e7968ca18074.exe 4160 69c1ec6b75fa73e29475e7968ca18074.exe - Suspicious use of WriteProcessMemory 45 IoCs
description pid Process procid_target PID 4160 wrote to memory of 4684 4160 69c1ec6b75fa73e29475e7968ca18074.exe 90 PID 4160 wrote to memory of 4684 4160 69c1ec6b75fa73e29475e7968ca18074.exe 90 PID 4160 wrote to memory of 4684 4160 69c1ec6b75fa73e29475e7968ca18074.exe 90 PID 4160 wrote to memory of 2576 4160 69c1ec6b75fa73e29475e7968ca18074.exe 92 PID 4160 wrote to memory of 2576 4160 69c1ec6b75fa73e29475e7968ca18074.exe 92 PID 4160 wrote to memory of 2576 4160 69c1ec6b75fa73e29475e7968ca18074.exe 92 PID 4160 wrote to memory of 412 4160 69c1ec6b75fa73e29475e7968ca18074.exe 99 PID 4160 wrote to memory of 412 4160 69c1ec6b75fa73e29475e7968ca18074.exe 99 PID 4160 wrote to memory of 412 4160 69c1ec6b75fa73e29475e7968ca18074.exe 99 PID 4160 wrote to memory of 2448 4160 69c1ec6b75fa73e29475e7968ca18074.exe 104 PID 4160 wrote to memory of 2448 4160 69c1ec6b75fa73e29475e7968ca18074.exe 104 PID 4160 wrote to memory of 2448 4160 69c1ec6b75fa73e29475e7968ca18074.exe 104 PID 4160 wrote to memory of 1940 4160 69c1ec6b75fa73e29475e7968ca18074.exe 106 PID 4160 wrote to memory of 1940 4160 69c1ec6b75fa73e29475e7968ca18074.exe 106 PID 4160 wrote to memory of 1940 4160 69c1ec6b75fa73e29475e7968ca18074.exe 106 PID 4160 wrote to memory of 3180 4160 69c1ec6b75fa73e29475e7968ca18074.exe 108 PID 4160 wrote to memory of 3180 4160 69c1ec6b75fa73e29475e7968ca18074.exe 108 PID 4160 wrote to memory of 3180 4160 69c1ec6b75fa73e29475e7968ca18074.exe 108 PID 4160 wrote to memory of 3820 4160 69c1ec6b75fa73e29475e7968ca18074.exe 110 PID 4160 wrote to memory of 3820 4160 69c1ec6b75fa73e29475e7968ca18074.exe 110 PID 4160 wrote to memory of 3820 4160 69c1ec6b75fa73e29475e7968ca18074.exe 110 PID 4160 wrote to memory of 2784 4160 69c1ec6b75fa73e29475e7968ca18074.exe 112 PID 4160 wrote to memory of 2784 4160 69c1ec6b75fa73e29475e7968ca18074.exe 112 PID 4160 wrote to memory of 2784 4160 69c1ec6b75fa73e29475e7968ca18074.exe 112 PID 4160 wrote to memory of 3192 4160 69c1ec6b75fa73e29475e7968ca18074.exe 114 PID 4160 wrote to memory of 3192 4160 69c1ec6b75fa73e29475e7968ca18074.exe 114 PID 4160 wrote to memory of 3192 4160 69c1ec6b75fa73e29475e7968ca18074.exe 114 PID 4160 wrote to memory of 548 4160 69c1ec6b75fa73e29475e7968ca18074.exe 116 PID 4160 wrote to memory of 548 4160 69c1ec6b75fa73e29475e7968ca18074.exe 116 PID 4160 wrote to memory of 548 4160 69c1ec6b75fa73e29475e7968ca18074.exe 116 PID 4160 wrote to memory of 4220 4160 69c1ec6b75fa73e29475e7968ca18074.exe 118 PID 4160 wrote to memory of 4220 4160 69c1ec6b75fa73e29475e7968ca18074.exe 118 PID 4160 wrote to memory of 4220 4160 69c1ec6b75fa73e29475e7968ca18074.exe 118 PID 4160 wrote to memory of 4320 4160 69c1ec6b75fa73e29475e7968ca18074.exe 120 PID 4160 wrote to memory of 4320 4160 69c1ec6b75fa73e29475e7968ca18074.exe 120 PID 4160 wrote to memory of 4320 4160 69c1ec6b75fa73e29475e7968ca18074.exe 120 PID 4160 wrote to memory of 3860 4160 69c1ec6b75fa73e29475e7968ca18074.exe 122 PID 4160 wrote to memory of 3860 4160 69c1ec6b75fa73e29475e7968ca18074.exe 122 PID 4160 wrote to memory of 3860 4160 69c1ec6b75fa73e29475e7968ca18074.exe 122 PID 4160 wrote to memory of 3424 4160 69c1ec6b75fa73e29475e7968ca18074.exe 124 PID 4160 wrote to memory of 3424 4160 69c1ec6b75fa73e29475e7968ca18074.exe 124 PID 4160 wrote to memory of 3424 4160 69c1ec6b75fa73e29475e7968ca18074.exe 124 PID 4160 wrote to memory of 2584 4160 69c1ec6b75fa73e29475e7968ca18074.exe 126 PID 4160 wrote to memory of 2584 4160 69c1ec6b75fa73e29475e7968ca18074.exe 126 PID 4160 wrote to memory of 2584 4160 69c1ec6b75fa73e29475e7968ca18074.exe 126
Processes
-
C:\Users\Admin\AppData\Local\Temp\69c1ec6b75fa73e29475e7968ca18074.exe"C:\Users\Admin\AppData\Local\Temp\69c1ec6b75fa73e29475e7968ca18074.exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4160 -
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:4684
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:2576
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:412
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:2448
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:1940
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:3180
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:3820
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:2784
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:3192
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:548
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:4220
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:4320
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:3860
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:3424
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:2584
-