File scan report
Verdict Suspicious
Is steamclient_ loader. exe safe? Treat it as suspicious.
Unsigned 1201-day-old EXE with 17/70 detections, mostly less reliable, and benign network activity.
Why Suspicious? 17 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as unverified; obtain Steam client components only from official Valve distribution channels.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
17 of 70 flagged
- Flagged 17
- No detection 53
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
2 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
One major antivirus engine flags it as PossibleThreat while 15 major antivirus engines report clean.
The one detection from a major antivirus engine is generic and not corroborated by other major antivirus engines. Widespread distribution over three years and clean sandbox verdict reduce risk, yet the unsigned status and mixed less reliable detections keep the file in the suspicious band.
What We Detected
17 of the 70 antivirus engines that checked it flagged the sample; only Fortinet (major) returned a named detection (W32/PossibleThreat). No code signing certificate is present.
Threat Behavior
Sandbox execution produced only MITRE techniques common in legitimate software and contacted Microsoft/Akamai infrastructure plus the standard NCSI connectivity check. no complete contacted-host reputation result was available, files it created, or persistence mechanisms were observed.
What To Do Now
Keep Windows Defender and other security software enabled. If the file was obtained from an untrusted source, replace it with a verified copy from the legitimate Steam distribution channel.
Where this verdict could be wrong1 caveat
- communityComments include three FileScan.IO reports claiming MALICIOUS with 100/100 confidence, though these are third-party annotations without major antivirus engine backing.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- widely seen and long established prevalence (3682 sources)
- no malicious sandbox verdict
- unsigned executable
- 17 engines flagged (1 major)
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 9sandbox rule tags
- 2spawned processes
- 4network contacts
- 36filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
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.
Note: Connected to 4 servers during the test run.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; 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.
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
steamclient_loader.exe
6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
GUM7CCC.tmp
C:\Program Files\Google\Temp\GUM7CCC.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
GUMA43B.tmp
C:\Program Files\Google\Temp\GUMA43B.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
23.209.116.25
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
20.22.113.133
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 9 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
17 of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 17
- Fortinet (major engine)W32/PossibleThreat
- TrellixENS (major engine)GenericRXAA-AA!2A64F1E0FBB0
- Antiy-AVLTrojan/Win32.Agent
- APEXMalicious
- CAT-QuickHealTrojan.Riskware
- CTXexe.trojan.generic
- CylanceUnsafe
- GridinsoftTrojan.Win32.Gen.cl
File fingerprint
- Last analyzed
- Aug 22, 2026, 3:28 PM UTC
- SHA-256
6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0- SHA-1
5601fd7b42835ba56fb13e0fe1915964ab0a42e4- MD5
2a64f1e0fbb0e0687bd41dedf3ab19e8
About this file
steamclient_loader.exe is a Win32 EXE file of 100.9 kB.
- Type and size
- Win32 EXE · 100.9 kB
- Signer
- UnsignedNo code signature.
- First seen
- May 9, 2023On VirusTotal.
- Submitted by
- 3,682 distinct sources
- Packer
- None detected
- Entropy
- 6.07 of 8
First scanned
Includes every engine result (75), PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is steamclient_loader.exe safe, or is it malware?
What is steamclient_loader.exe?
How many antivirus engines detected steamclient_loader.exe?
What should I do if I already ran steamclient_loader.exe?
What is the SHA-256 hash of steamclient_loader.exe?
How up to date is this analysis of steamclient_loader.exe?
Community
Member reviews and reports for this exact file hash.