Analysis
-
max time kernel
145s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
29-01-2023 21:29
Static task
static1
Behavioral task
behavioral1
Sample
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe
Resource
win7-20221111-en
General
-
Target
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe
-
Size
417KB
-
MD5
eba584dbe102dea11a92683e90bc5306
-
SHA1
3ec661ea74194a24a1468ea932c0f658bdf1080c
-
SHA256
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2
-
SHA512
6d1f7874809b1416be371be2dbeefa79e0ecbaf782a2800c4a6b6537ef408d3f1c6d13842937dd055e5941d31d3884348d69d0d25a545e43bcd67e6ecadea4e1
-
SSDEEP
12288:NomltV+kni0u8wHEnjQHyUjCa9q9Zsdk:pKFHXj/9q9KS
Malware Config
Extracted
asyncrat
0.5.7B
Default
0.tcp.ngrok.io:6032
Asyn♦cMutex_6SI8OkPnk
-
delay
3
-
install
false
-
install_file
svchost.exe
-
install_folder
%AppData%
Signatures
-
Async RAT payload 1 IoCs
Processes:
resource yara_rule behavioral2/memory/3564-142-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\Control Panel\International\Geo\Nation 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exedescription pid process target process PID 5064 set thread context of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
-
Suspicious behavior: EnumeratesProcesses 7 IoCs
Processes:
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exepid process 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exedescription pid process Token: SeDebugPrivilege 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe -
Suspicious use of WriteProcessMemory 17 IoCs
Processes:
3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exedescription pid process target process PID 5064 wrote to memory of 2844 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe schtasks.exe PID 5064 wrote to memory of 2844 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe schtasks.exe PID 5064 wrote to memory of 2844 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe schtasks.exe PID 5064 wrote to memory of 4288 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 4288 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 4288 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 4344 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 4344 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 4344 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe PID 5064 wrote to memory of 3564 5064 3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe MSBuild.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe"C:\Users\Admin\AppData\Local\Temp\3a617a7952e9ea3f03052844e4ed2e0262c937d5c62de5e1753ec23dbde3e4a2.exe"1⤵
- Checks computer location settings
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\schtasks.exe"C:\Windows\System32\schtasks.exe" /Create /TN "Updates\QxJiZoTYrf" /XML "C:\Users\Admin\AppData\Local\Temp\tmp37C9.tmp"2⤵
- Creates scheduled task(s)
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"{path}"2⤵
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"{path}"2⤵
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"{path}"2⤵
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Temp\tmp37C9.tmpFilesize
1KB
MD573cc86a3c13f7009153dca434ef7a04c
SHA109cdb394635bfb61ce0971054ded5c4a0825cacd
SHA256c55a941221b81f9d3612c8590e7f622bce08b574c83c9474cad7662f3a337bd7
SHA512d28ce59d31da3ca0b1c20e1fd59264c092f17f62a67d1c9023d69afe0c1700af299326ab9054ae2057f6a468f6dc7b836cb411b1096de84780347ba9411e6c95
-
memory/2844-137-0x0000000000000000-mapping.dmp
-
memory/3564-141-0x0000000000000000-mapping.dmp
-
memory/3564-142-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/4288-139-0x0000000000000000-mapping.dmp
-
memory/4344-140-0x0000000000000000-mapping.dmp
-
memory/5064-132-0x00000000009D0000-0x0000000000A40000-memory.dmpFilesize
448KB
-
memory/5064-133-0x0000000008040000-0x00000000085E4000-memory.dmpFilesize
5.6MB
-
memory/5064-134-0x0000000007C70000-0x0000000007D02000-memory.dmpFilesize
584KB
-
memory/5064-135-0x0000000007C50000-0x0000000007C5A000-memory.dmpFilesize
40KB
-
memory/5064-136-0x000000000B540000-0x000000000B5DC000-memory.dmpFilesize
624KB