Analysis
-
max time kernel
162s -
max time network
186s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
-
submitted
04-01-2024 04:36
General
-
Target
3fe910d9adfd6c79df72aa9e5b3f3db4.pdf
-
Size
41KB
-
MD5
3fe910d9adfd6c79df72aa9e5b3f3db4
-
SHA1
ad19eb5cbb19e620a5c15c3798dc847fd33cd8ed
-
SHA256
58952eaa8fd918a672c62251937c08fc432e6834391779e360396dd01ca002e9
-
SHA512
fff0b47036e156c683990056135f0c207bfe1b367dd4c2ccdd43bf207d7c4610d408dd923a3fe01fb041cacb977a4bda494d0a3729a161df8fcbf6de7a20b481
-
SSDEEP
768:Ew4w1Cqdq0sPSNxHb+s6DKA1dVhljfHdmnRu7tTUYrukgE18sCNF:EwqU+shABh1Y6tQYrTD8tF
Score
1/10
Malware Config
Signatures
-
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
-
Suspicious use of SetWindowsHookEx 4 IoCs
Processes
-
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe"C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe" "C:\Users\Admin\AppData\Local\Temp\3fe910d9adfd6c79df72aa9e5b3f3db4.pdf"1⤵
- Checks processor information in registry
- Suspicious use of SetWindowsHookEx