General
- Target Creative EAX c.exe
- Size 16.1MB
- Sample260623-mcl33sby8p
- SHA256 79b1fd99a02661d3e6d661dbe3fda257fba44e4958c26cf8f14e220d37944c4e
- MD5 b9cbd07a2b4688f40e4ec1106315c8a3
- SHA1 769a7e895da6399e16658e2825083cb9265da58d
- SHA512 bf39bb0d6b1fb68f4f48cc8ff41f006c668e866cb4feeb15a761f66f5705226b188f02195cfd5f4907f9020ff5a0713b89157c96ae3913252014ee44c7ed114b
- SSDEEP 393216:iEkIrsOvDKIlA8lBnghNpv3m8xXhW1IcjBU0:iEFrsOrrlrchHLxXJcjBU
- TLSH T16207335120DCB2DEA630A47FEADF2403AE472599EEF75762324C1AB1CDDC60112B7276
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
Creative EAX c.exe
Resource
win10v2004-20260513-en
Behavioral task
behavioral2
Sample
Creative EAX c.exe
Resource
ubuntu2204-amd64-20260513-en
Behavioral task
behavioral3
Sample
Creative EAX c.exe
Resource
debian9-armhf-20260513-en
Behavioral task
behavioral4
Sample
Creative EAX c.exe
Resource
debian9-mipsbe-20260513-en
Behavioral task
behavioral5
Sample
Creative EAX c.exe
Resource
debian9-mipsel-20260513-en
Malware Config
Targets
-
- Target Creative EAX c.exe
- Size 16.1MB
- SHA256 79b1fd99a02661d3e6d661dbe3fda257fba44e4958c26cf8f14e220d37944c4e
- MD5 b9cbd07a2b4688f40e4ec1106315c8a3
- SHA1 769a7e895da6399e16658e2825083cb9265da58d
- SHA512 bf39bb0d6b1fb68f4f48cc8ff41f006c668e866cb4feeb15a761f66f5705226b188f02195cfd5f4907f9020ff5a0713b89157c96ae3913252014ee44c7ed114b
- SSDEEP 393216:iEkIrsOvDKIlA8lBnghNpv3m8xXhW1IcjBU0:iEFrsOrrlrchHLxXJcjBU
- TLSH T16207335120DCB2DEA630A47FEADF2403AE472599EEF75762324C1AB1CDDC60112B7276
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Suspicious use of NtCreateUserProcessOtherParentProcess
-
Sets service image path in registry
This determines the executable launched when a service starts. It can be used to establish persistence.
-
Checks BIOS information in registry
BIOS information is often read in order to detect sandboxing environments.
-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
Executes dropped EXE
-
Indicator Removal: Clear Windows Event Logs
Clear Windows Event Logs to hide the activity of an intrusion.
-
Loads dropped DLL
-
Enumerates connected drives
Attempts to read the root path of hard drives other than the default C: drive.
-
Writes to the Master Boot Record (MBR)
Bootkits write to the MBR to gain persistence at a level below the operating system.
-
Drops file in System32 directory
-
Suspicious use of SetThreadContext
MITRE ATT&CK Enterprise v16
Persistence
Boot or Logon Autostart Execution
1Registry Run Keys / Startup Folder
1Create or Modify System Process
1Windows Service
1Pre-OS Boot
1Bootkit
1Scheduled Task/Job
1Scheduled Task
1Privilege Escalation
Boot or Logon Autostart Execution
1Registry Run Keys / Startup Folder
1Create or Modify System Process
1Windows Service
1Scheduled Task/Job
1Scheduled Task
1Defense Evasion
Indicator Removal
1Clear Windows Event Logs
1Modify Registry
1Pre-OS Boot
1Bootkit
1