af32cbcb4b8af657c7fa6b7945d4dd6d6410e23e2a5de13f8498096acf63c2b2

Analysis

max time kernel
121s
max time network
125s
platform
windows7_x64
resource
win7-20240903-en
resource tags

arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system
submitted
02-12-2024 17:27

Target

xolborheck.exe
Size

7.6MB
MD5

532c9e5da2905d241e932d58f302ec68
SHA1

e4cb610e0b5284c8effa8bf270dfed8f27b455fe
SHA256

af32cbcb4b8af657c7fa6b7945d4dd6d6410e23e2a5de13f8498096acf63c2b2
SHA512

f0438b9e29b523bd3a3f755de9d365b994c1471be3e898aae3c183fbe44d462d8928a68dae72305b481305860434981e3cd067850dd6c97fdd79ad84c735da44
SSDEEP

196608:igHY42wfI9jUCzi4H1qSiXLGVi7DMgpZ3Q0VMwICEc/j6:H9IHziK1piXLGVE4Ue0VJG

Score

7^/10

upx

Loads dropped DLL 1 IoCs

pid	Process
2684	xolborheck.exe

UPX packed file 2 IoCs

Detects executables packed with UPX/modified UPX open source packer.

resource	yara_rule
behavioral1/files/0x000500000001924c-21.dat	upx
behavioral1/memory/2684-23-0x000007FEF67F0000-0x000007FEF6E53000-memory.dmp	upx

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 1868 wrote to memory of 2684	1868	xolborheck.exe	30
PID 1868 wrote to memory of 2684	1868	xolborheck.exe	30
PID 1868 wrote to memory of 2684	1868	xolborheck.exe	30

C:\Users\Admin\AppData\Local\Temp\xolborheck.exe
"C:\Users\Admin\AppData\Local\Temp\xolborheck.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:1868
- C:\Users\Admin\AppData\Local\Temp\xolborheck.exe
  "C:\Users\Admin\AppData\Local\Temp\xolborheck.exe"
  2⤵
  - Loads dropped DLL
  PID:2684

C:\Users\Admin\AppData\Local\Temp\_MEI18682\python313.dll

Filesize
1.8MB

MD5
6ef5d2f77064df6f2f47af7ee4d44f0f

SHA1
0003946454b107874aa31839d41edcda1c77b0af

SHA256
ab7c640f044d2eb7f4f0a4dfe5e719dfd9e5fcd769943233f5cece436870e367

SHA512
1662cc02635d63b8114b41d11ec30a2af4b0b60209196aac937c2a608588fee47c6e93163ea6bf958246c32759ac5c82a712ea3d690e796e2070ac0ff9104266

Download Submit
memory/2684-23-0x000007FEF67F0000-0x000007FEF6E53000-memory.dmp

Filesize
6.4MB

Download