Analysis
-
max time kernel
23s -
max time network
17s -
platform
windows7_x64 -
resource
win7-20240903-en -
resource tags
arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system -
submitted
17-10-2024 16:53
Behavioral task
behavioral1
Sample
68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe
Resource
win7-20240903-en
windows7-x64
2 signatures
300 seconds
Behavioral task
behavioral2
Sample
68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe
Resource
win10v2004-20241007-en
windows10-2004-x64
1 signatures
300 seconds
General
-
Target
68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe
-
Size
4KB
-
MD5
3d062a5923050f0885aa5e4882096744
-
SHA1
9162c4e04cfa48296a77ce2aa92c79f799e2a32d
-
SHA256
68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060
-
SHA512
f1853c28664ff8fd9f3ce3a6b69dc16737e90f4379cf80cc39742f607764a433984c7909910181b34f364028c1dfb21395b2768a54367a1d2fc995b26ff64d70
Score
5/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/3044-0-0x000000013F640000-0x000000013F648000-memory.dmp upx behavioral1/memory/3044-1-0x000000013F640000-0x000000013F648000-memory.dmp upx -
Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 3044 wrote to memory of 2436 3044 68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe 30 PID 3044 wrote to memory of 2436 3044 68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe 30 PID 3044 wrote to memory of 2436 3044 68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe"C:\Users\Admin\AppData\Local\Temp\68b536fb2a6a8c9a2b36e17ead46343d156020c75c559ed068483ecf5bc3f060.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:3044 -
C:\Windows\system32\WerFault.exeC:\Windows\system32\WerFault.exe -u -p 3044 -s 322⤵PID:2436
-
-
C:\Windows\explorer.exe"C:\Windows\explorer.exe"1⤵PID:1848