File scan report
Verdict Malicious
Is Process. exe safe? No, we rate this exact file malicious.
Fifty-two of the 69 antivirus engines that checked it flagged this executable, while sandbox evidence recorded code injection into svchost.exe and multiple engines identified…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
52 of 69 flagged
- Flagged 52
- No detection 17
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 14y ago
Chapter 02
Why we think so
5 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This unsigned executable has extensive detection support: 52 of the 69 antivirus engines that checked it flagged it, including 10 major antivirus engines, and several labels identify Sasfis. Sandbox evidence also recorded injection into svchost.exe, although the combined runtime verdicts were split between malware and clean results.
The antivirus evidence is overwhelming, with 52 of the 69 antivirus engines that checked it flagging the file and 41 independent detection votes. Ten major antivirus engines detected it, and multiple engines—including Kaspersky—used the Sasfis family name. The sandbox recorded code injection into svchost.exe, providing concrete support for the process-injection labels rather than relying on a technique mapping alone. A hacking-tool label was also corroborated across the engine results. Although another sandbox result was clean and the inspected contacted hosts were not flagged, those counter-signals do not plausibly outweigh the broad engine agreement and named injection target.
What We Detected
Fifty-two of the 69 antivirus engines that checked it flagged the executable, representing 41 independent detection votes. Ten major antivirus engines detected it, and several engines identified the Sasfis family or process-hijacking behavior. The file is unsigned, so there is no verified publisher identity to counter those findings.
Threat Behavior
Sandbox evidence recorded code injection into the Windows service-host process, matching T1055 and T1055.012. This is a concrete named target and corroborates the engine labels describing injection or process hijacking. Runtime results were split, with one result reporting malware and another reporting clean, but the recorded injection and extensive engine detections provide independent support. The complete reputation check of observed contacts found no known-malicious or known-suspicious hosts.
What To Do Now
Do not run the executable. Quarantine or remove it with security software kept enabled, and inspect the affected system for unexpected processes or persistence if it was already executed.
Where this verdict could be wrong3 caveats
- The sandbox results were split: malicious activity was reported, but another result was clean.
- The complete host-reputation cross-check found no known-malicious or known-suspicious host among 22 inspected contacts.
- No malicious file it created was identified, and the antivirus analysis found no packing or high-entropy code.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The complete reputation check found no known-malicious or known-suspicious host among 22 inspected contacts.
- No malicious file it created was identified.
- The antivirus analysis found no packer or high-entropy code.
- Fifty-two of the 69 antivirus engines that checked it flagged the executable, including 10 major antivirus engines.
- Multiple engines identified the Sasfis family or process-hijacking behavior.
- Sandbox evidence recorded injection into the Windows service-host process.
- The executable has no verified publisher signature.
- Multiple engine labels corroborated hacking-tool functionality.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 10 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 10isolated sandbox runs
- 10sandbox rule tags
- 15spawned processes
- 4network contacts
- 25filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
High concern: Injected code into another program on the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as loading code in memory; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Process.exe
dc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
44861457bece1d1906df89f0e66a46nalysis_subject.exe
C:\Users\Elijah\AppData\Local\Temp\44861457bece1d1906df89f0e66a46nalysis_subject.exe
Test run - Evidence 3 of 7: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
helloworld.exe
c:\analyse\helloworld.exe
Test run - Evidence 5 of 7: Written fileSeen in the test run
helloworld.exe
C:\Users\user\Desktop\helloworld.exe
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
www.msn.com.edgekey.net
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
e592.d.akamaiedge.net
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 10 sandboxes and the results were split: 1 returned "malicious" and 1 returned "clean".
Sandbox verdicts
2- VT: MALWAREmalicious
- VT: CLEANclean
Techniques observed in the sandbox
10MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1036
- T1055· Process injection
- T1055.012· Process injection
- T1071· Application protocol
- T1071.001· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1202
- T1620· In-memory loading
Observed activity
Processes started
14Programs the file ran, with their command lines.
44861457bece1d1906df89f0e66a46nalysis_subject.exeC:\Users\Elijah\AppData\Local\Temp\44861457bece1d1906df89f0e66a46nalysis_subject.execmd.exeC:\Windows\SysWOW64\cmd.exe44861457BECE1D1906DF89F0E66A46BB.exe%SAMPLEPATH%\44861457BECE1D1906DF89F0E66A46BB.exesvchost.exeC:\Windows\SysWOW64\svchost.exedc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b.exe%SAMPLEPATH%\dc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b.execmd.exeC:\Windows\System32\cmd.exe
Show all 14 entries for processes started
dc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b.exeC:\dc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b.exesvchostcmd.exeC:\Windows\system32\cmd.exe /c pausesvchost.exeC:\WINDOWS\system32\svchost.execmd.exeC:\WINDOWS\system32\cmd.exe C:\WINDOWS\system32\cmd.exe /c pausefile.exe"C:\Users\user\Desktop\file.exe"svchost.exeC:\Windows\SysWOW64\svchost.exe svchostcmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c pause
Code injected into
1Other programs the file wrote its code into while it ran.
C:\WINDOWS\system32\svchost.exe
Network contacts
44 hosts, listed as 2 domains, 2 addresses. Links show the host and path only.
- Domain
www.msn.com.edgekey.net - Domain
e592.d.akamaiedge.net - IP address
23.53.122.135 - IP address
104.98.118.178
Files
24Files the file created, changed or deleted.
- Written
c:\analyse\helloworld.exe - Written
C:\Users\user\Desktop\helloworld.exe - Written
\Device\ConDrv - Written
\Device\ConDrv\\Connect - Written
C:\Users\user\AppData\Local\Packages\Microsoft.WidgetsPlatformRuntime_8wekyb3d8bbwe\LocalState\FeedSessions\MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy!Widgets!!com.msn.desktopfeed - Written
C:\Users\user\AppData\Local\Packages\Microsoft.WidgetsPlatformRuntime_8wekyb3d8bbwe\LocalState\FeedSessions\MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy!Widgets!!com.msn.desktopfeed\027a33a6-6042-430f-9d66-ffc4cfa7f559.dat
Show all 24 entries for files
- Written
C:\Users\user\AppData\Local\Packages\Microsoft.WidgetsPlatformRuntime_8wekyb3d8bbwe\LocalState\FeedSessions\MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy!Widgets!!com.msn.desktopfeed\027a33a6-6042-430f-9d66-ffc4cfa7f559.dat.~tmp - Written
C:\Users\user\AppData\Local\Packages\Microsoft.WidgetsPlatformRuntime_8wekyb3d8bbwe\LocalState\FeedSessions\MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy!Widgets!!com.msn.desktopfeed\027a33a6-6042-430f-9d66-ffc4cfa7f559.dat~RF3cd57c.TMP - Written
C:\Users\user\AppData\Local\Packages\Microsoft.WidgetsPlatformRuntime_8wekyb3d8bbwe\LocalState\FeedSessions\MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy!Widgets!!com.msn.desktopfeed\027a33a6-6042-430f-9d66-ffc4cfa7f559.dat~RF3cd82c.TMP - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER37E3.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B6E.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BDC.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FD1.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5020.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5041.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E60.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F1C.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F3C.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER243D.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER244E.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER244F.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER47F.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8.tmp.csv
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
ShimCacheMutex
Sandbox background — not the file
29The analysis machine's own processes and connections, recorded in every run.
- VM injection target
\\?\C:\Windows\system32\wbem\WMIADAP.EXE - VM injection target
C:\Program Files\Google2876_168642522\bin\updater.exe - VM injection target
C:\Program Files\Google3960_1988869807\bin\updater.exe - VM host
www.microsoft.com - VM host
res.public.onecdn.static.microsoft - VM host
windows.msn.com-ion.edgesuite.net
Show all 29 entries for sandbox background — not the file
- VM host
a1672.dscr.akamai.net - VM host
www.msn.com - VM host
assets.msn.com - VM host
assets.msn.com-ion.edgesuite.net - VM host
a1666.dscr.akamai.net - VM host
a83f:8110:0:0:0:5:0:0 - VM host
23.216.147.64 - VM host
a83f:8110:0:0:100:0:1800:0 - VM host
23.216.147.76 - VM host
a83f:8110:c579:d801:beac:bf78:cce1:d301 - VM host
20.99.132.105 - VM host
a83f:8110:6f00:7200:6100:7400:6900:6f00 - VM host
20.99.133.109 - VM host
192.168.0.1 - VM host
192.229.211.108 - VM host
a83f:8110:0:0:2000:0:0:0 - VM host
20.99.185.48 - VM host
a83f:8110:3048:400:a0:4904:0:104b - VM host
20.99.186.246 - VM host
20.99.184.37 - VM host
192.168.0.53 - VM host
151.101.22.172 - VM host
23.55.140.42
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- c60f06d62d51be360fbd…621716Not checkedno saved verdict
- 9f8fc38cb5d317c0ba29…77f4f0Not checkedno saved verdict
- f20aea9bcefa8cfff6a1…c4c190Not checkedno saved verdict
Chapter 04
Technical details
52 of the 69 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 52
- Avira (major engine)TR/W32.Dh.A
- BitDefender (major engine)Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- DrWeb (major engine)Trojan.Inject2.18900
- Emsisoft (major engine)Gen:Trojan.ProcessHijack.auW@a8yLeLmi (B)
- F-Secure (major engine)Trojan.TR/W32.Dh.A
- Fortinet (major engine)W32/Generic.AP.3318F0!tr
- GData (major engine)Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- Kaspersky (major engine)Trojan.Win32.Sasfis.edwh
File fingerprint
- Last analyzed
- Nov 1, 2026, 12:13 PM UTC
- SHA-256
dc96fff187e9aa4da179a3b7b9f6a8fe3ab4e0a073b6b8d55e83c6d075bc957b- SHA-1
f00d8ed46106523d8413fe9432ef74b00f98bf14- MD5
44861457bece1d1906df89f0e66a46bb
About this file
Process.exe is a Win32 EXE file of 10.8 kB.
- Type and size
- Win32 EXE · 10.8 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 31, 2012On VirusTotal.
- Submitted by
- 106 distinct sources
- Packer
- None detected
- Entropy
- 5.03 of 8
First scanned
Antivirus consensus
52 of 69 engines flagged this file
6 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 52 detections come from 41 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-116 engines10flagged14 vendors sharing 10 engines
- Tier-236 engines21flagged25 vendors sharing 21 engines
- Low-trust17 engines13flagged
View all 75 engine results
- AhnLab-V3Malicious: Trojan/Win32.RL_Sasfis.R304038
- AlibabaMalicious: Trojan:Win32/Sasfis.0838dc3a
- alibabacloudMalicious: Trojan[downloader]:Win/Redosdru
- ALYacMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- Antiy-AVLMalicious: Trojan/Win32.Sasfis
- ArcabitMalicious: Trojan.ProcessHijack.EE9CF6
- AviraMalicious: TR/W32.Dh.A
- BitDefenderMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- BkavMalicious: W32.Malware.D56E0DD4
- ClamAVMalicious: Win.Packed.Zusy-9880177-0
- CrowdStrikeMalicious: win/malicious_confidence_100% (W)
- CTXMalicious: exe.trojan.processhijack
- CylanceMalicious: Unsafe
- CynetMalicious: Malicious (score: 99)
- DeepInstinctMalicious: MALICIOUS
- DrWebMalicious: Trojan.Inject2.18900
- ElasticMalicious: malicious (moderate confidence)
- EmsisoftMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi (B)
- F-SecureMalicious: Trojan.TR/W32.Dh.A
- FortinetMalicious: W32/Generic.AP.3318F0!tr
- GDataMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- GoogleMalicious: Detected
- huorongMalicious: HVM:Trojan/Injector.dy
- JiangminMalicious: Trojan/Sasfis.absf
- K7AntiVirusMalicious: Riskware ( 0040eff71 )
- K7GWMalicious: Riskware ( 0040eff71 )
- KasperskyMalicious: Trojan.Win32.Sasfis.edwh
- KingsoftMalicious: Win32.Trojan.Sasfis.edwh
- LionicMalicious: Trojan.Win32.Sasfis.trIz
- MalwarebytesMalicious: Generic.Malware/Suspicious
- MaxSecureMalicious: Trojan.Malware.6902232.susgen
- McAfeeDMalicious: ti!DC96FFF187E9
- MicrosoftMalicious: Trojan:MSIL/Cryptor!rfn
- MicroWorld-eScanMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- NANO-AntivirusMalicious: Trojan.Win32.Sasfis.cxfpoh
- PaloaltoMalicious: generic.ml
- PandaMalicious: PUP/Hacktool
- RisingMalicious: Trojan.Sasfis!8.16C4 (TFE:5:qjUTt3fKypH)
- SangforMalicious: Trojan.Win32.Sasfis.Vw7e
- SkyhighMalicious: BehavesLike.Win32.Injector.lm
- SophosMalicious: Mal/Generic-S
- SymantecMalicious: ML.Attribute.HighConfidence
- TencentMalicious: Malware.Win32.Gencirc.13b26cc2
- TrellixENSMalicious: GenericRXAA-AA!44861457BECE
- TrendMicroMalicious: HackTool.Win32.Sasfis.AA
- TrendMicro-HouseCallMalicious: HackTool.Win32.Sasfis.AA
- VaristMalicious: W32/ABTrojan.EXLL-0149
- VBA32Malicious: Malware-Cryptor.Inject.gen
- VIPREMalicious: Gen:Trojan.ProcessHijack.auW@a8yLeLmi
- VirITMalicious: Trojan.Win32.Inject2.BBYY
- XcitiumMalicious: Malware@#16u1o4c56fz1
- YandexMalicious: Trojan.GenAsa!qH5gXiIU31I
- AcronisClean
- APEXClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- BitDefenderFalxNo result
- CAT-QuickHealClean
- CMCClean
- ESET-NOD32Clean
- GridinsoftClean
- IkarusClean
- SentinelOneClean
- SUPERAntiSpywareClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TrapmineClean
- TrustlookNo result
- ViRobotClean
- WebrootClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The sandbox recorded code injection into the process quoted below (MITRE T1055). Injecting into another process is a common way to hide malicious code inside a legitimate one.
EvidenceC:\WINDOWS\system32\svchost.exe
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is Process.exe malware?
What is Process.exe?
How many antivirus engines detected Process.exe?
I already downloaded and ran Process.exe — what should I do?
How do I remove Process.exe?
What kind of malware is Process.exe?
What is the SHA-256 hash of Process.exe?
How up to date is this analysis of Process.exe?
Community
Member reviews and reports for this exact file hash.