c1de15b5d043dd79dd267dd5f6d8f3ea9e15bc8a2ab63cb5fb4080cb4804c18e

Analysis

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

arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system
submitted
21-11-2024 18:12

Target

Celery.exe
Size

17.8MB
MD5

9456cbd8d57d7a61d899aae79b5ee862
SHA1

42135056c2f963cb94edeaac23f7c0eed1cde6b3
SHA256

24e427fe676e2b9ca98c7fc0179ed4c8ee058500072ad645d554ffeb2f072ab6
SHA512

c71030da342ba2c8d589c3f93e71c54d4578a16587787e0b4b3d97bf5a9bd6c49d282b117f695d27b3438f3affe5fc715cc5f587e6c3e679ea125c0cbfe2c057
SSDEEP

393216:2qPnLFXlrPmQ8DOETgsvfGF0gK8mvE9cUSdOibq:bPLFXNOQhEtdqFSde

Score

7^/10

upx

Loads dropped DLL 1 IoCs

pid	Process
3032	Celery.exe

UPX packed file 2 IoCs

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

resource	yara_rule
behavioral27/files/0x000500000001c870-111.dat	upx
behavioral27/memory/3032-113-0x000007FEF62B0000-0x000007FEF671E000-memory.dmp	upx

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 2060 wrote to memory of 3032	2060	Celery.exe	31
PID 2060 wrote to memory of 3032	2060	Celery.exe	31
PID 2060 wrote to memory of 3032	2060	Celery.exe	31

C:\Users\Admin\AppData\Local\Temp\Celery.exe
"C:\Users\Admin\AppData\Local\Temp\Celery.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2060
- C:\Users\Admin\AppData\Local\Temp\Celery.exe
  "C:\Users\Admin\AppData\Local\Temp\Celery.exe"
  2⤵
  - Loads dropped DLL
  PID:3032

C:\Users\Admin\AppData\Local\Temp\_MEI20602\python310.dll

Filesize
1.4MB

MD5
69d4f13fbaeee9b551c2d9a4a94d4458

SHA1
69540d8dfc0ee299a7ff6585018c7db0662aa629

SHA256
801317463bd116e603878c7c106093ba7db2bece11e691793e93065223fc7046

SHA512
8e632f141daf44bc470f8ee677c6f0fdcbcacbfce1472d928576bf7b9f91d6b76639d18e386d5e1c97e538a8fe19dd2d22ea47ae1acf138a0925e3c6dd156378

Download Submit
memory/3032-113-0x000007FEF62B0000-0x000007FEF671E000-memory.dmp

Filesize
4.4MB

Download