Analysis
-
max time kernel
155s -
max time network
169s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
30-05-2022 23:26
Static task
static1
Behavioral task
behavioral1
Sample
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe
Resource
win10v2004-20220414-en
General
-
Target
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe
-
Size
113KB
-
MD5
925e4d90dd6e583fcae285beceb18222
-
SHA1
9555fe5f2ef656796ec3d88d027591fb403d2cde
-
SHA256
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff
-
SHA512
d9dde221336f17c594818a62a29da49ef39908703cda3d59db28fdaa8812414848e644c0e135f774d17e78abaedb047d1f6546e675b2e1f9a153cc82a9686b3e
Malware Config
Signatures
-
suricata: ET MALWARE Generic - POST To .php w/Extended ASCII Characters
suricata: ET MALWARE Generic - POST To .php w/Extended ASCII Characters
-
suricata: ET MALWARE Ransomware Locky CnC Beacon 2
suricata: ET MALWARE Ransomware Locky CnC Beacon 2
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exedescription pid process target process PID 384 set thread context of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exedescription pid process target process PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe PID 384 wrote to memory of 2760 384 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe 081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe"C:\Users\Admin\AppData\Local\Temp\081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:384 -
C:\Users\Admin\AppData\Local\Temp\081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe"C:\Users\Admin\AppData\Local\Temp\081917f88a506d680c6364da06476c69b5b65bdabae41151518d928d6ba429ff.exe"2⤵PID:2760
-