Analysis
-
max time kernel
101s -
max time network
131s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
07-07-2022 08:36
Static task
static1
Behavioral task
behavioral1
Sample
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe
Resource
win7-20220414-en
General
-
Target
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe
-
Size
632KB
-
MD5
467f93116f71b0e46d4db3f357b5be5d
-
SHA1
1f17d8cadfd4c84a0b8ce709a99a5ef787133bd4
-
SHA256
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8
-
SHA512
aaaf080f52fe4b6a9422e24ccaef42cbc626101888b83251bbb0c085ba033f734ccdc7b7a98cbef20e4ecde4e3cceef0a1e99e79f0e9feb3dd6f2aa5c12268c6
Malware Config
Extracted
lokibot
http://davuchi.eroea.com/fre.php
http://kbfvzoboss.bid/alien/fre.php
http://alphastand.trade/alien/fre.php
http://alphastand.win/alien/fre.php
http://alphastand.top/alien/fre.php
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exedescription pid process target process PID 400 set thread context of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exepid process 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exedescription pid process target process PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe PID 400 wrote to memory of 428 400 a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe"C:\Users\Admin\AppData\Local\Temp\a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:400 -
C:\Users\Admin\AppData\Local\Temp\a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe"C:\Users\Admin\AppData\Local\Temp\a8929f5b21d92e37b1331a6e7b7c072bf87b77ba590783cfcb18e384b70860e8.exe"2⤵PID:428