Analysis
-
max time kernel
147s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
26/05/2024, 05:59
Static task
static1
Behavioral task
behavioral1
Sample
298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe
Resource
win10v2004-20240508-en
General
-
Target
298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe
-
Size
8.1MB
-
MD5
2e728ef3d65402d4a4e215e419829d9a
-
SHA1
72c3fbda02099ea0ff5e84796436d9587a2ca79f
-
SHA256
298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4
-
SHA512
05aa089101c78c270d80b770d463fd6573c329d7db2c45c233d74ab07645072d35d87691007e7cc6afa1f9e7fabaff1a9f25e8dece825d7256d6d0a3759e82b5
-
SSDEEP
196608:73/vkIReBmx7NKOUrzOJbo0PR/gEcd1iQHPA5vh:DkIResbQrzSDZIfvrHy
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1396-37-0x0000000000400000-0x0000000000F21000-memory.dmp upx behavioral1/memory/1396-41-0x0000000000400000-0x0000000000F21000-memory.dmp upx behavioral1/memory/1396-42-0x0000000000400000-0x0000000000F21000-memory.dmp upx behavioral1/memory/1396-47-0x0000000000400000-0x0000000000F21000-memory.dmp upx -
Enumerates connected drives 3 TTPs 21 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\J: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\S: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\U: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\E: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\G: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\Q: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\V: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\X: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\Z: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\I: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\M: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\W: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\O: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\P: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\L: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\N: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\R: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\T: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\Y: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\H: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe File opened (read-only) \??\K: 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\CentralProcessor\0 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe -
Enumerates system info in registry 2 TTPs 4 IoCs
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemVersion 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe Key opened \REGISTRY\MACHINE\Hardware\Description\System\BIOS 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemManufacturer 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28 PID 1368 wrote to memory of 1396 1368 298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe"C:\Users\Admin\AppData\Local\Temp\298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:1368 -
C:\Users\Admin\AppData\Local\Temp\298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe"C:\Users\Admin\AppData\Local\Temp\298acbfa347cec0cc32d702a65d878e7121d19bcf911955041c4e579942940e4.exe"2⤵
- Enumerates connected drives
- Checks processor information in registry
- Enumerates system info in registry
PID:1396
-