Analysis
-
max time kernel
2s -
max time network
38s -
platform
windows7_x64 -
resource
win7v20210408 -
submitted
13-05-2021 12:57
Static task
static1
Behavioral task
behavioral1
Sample
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe
Resource
win7v20210408
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe
Resource
win10v20210410
0 signatures
0 seconds
General
-
Target
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe
-
Size
91KB
-
MD5
4bb8e8a39a8a8a591d7c653e70b4dcdc
-
SHA1
d14af0cc6cd83a2214d44d48483bd6e36fc2d76e
-
SHA256
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1
-
SHA512
721880a30c972a1022b3953f4ddab6c308b1d64bc6f57f152de4497b754e7075b086d06dbf580f0d1f91805633022ef736ae0c10960e7a18433936a3f7bb5c5a
Score
4/10
Malware Config
Signatures
-
Drops file in Windows directory 1 IoCs
Processes:
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exedescription ioc process File opened for modification C:\Windows\OEWABLog.txt c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exepid process 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe -
Suspicious behavior: MapViewOfSection 19 IoCs
Processes:
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exepid process 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exedescription pid process Token: SeDebugPrivilege 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exedescription pid process target process PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 372 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe wininit.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 384 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe csrss.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 420 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe winlogon.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 468 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe services.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 476 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsass.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 484 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe lsm.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 588 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 668 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 740 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe PID 684 wrote to memory of 808 684 c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe svchost.exe
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"3⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵
-
C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R3⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵
-
C:\Windows\system32\csrss.exe%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=161⤵
-
C:\Windows\system32\wininit.exewininit.exe1⤵
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵
-
C:\Users\Admin\AppData\Local\Temp\c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe"C:\Users\Admin\AppData\Local\Temp\c5ceed35f0c3924d52c5082844060a4fb03f6c1d5df5a41b1610edcfa9d8cbc1.exe"2⤵
- Drops file in Windows directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/684-59-0x0000000075C71000-0x0000000075C73000-memory.dmpFilesize
8KB