Is steamclient_loader.exe safe?
Unsigned 1201-day-old EXE with 17/75 detections, mostly low-trust, and benign network activity.
One tier-1 engine flags it as PossibleThreat while 15 tier-1 engines report clean. The file is unsigned, common_old, and shows only ambient sandbox behaviour with no complete contacted-host reputation result was available contacts.
6d76785ff9806540c4…a90b419f22a5a0Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
One tier-1 engine flags it as PossibleThreat while 15 tier-1 engines report clean. The file is unsigned, common_old, and shows only ambient sandbox behaviour with no complete contacted-host reputation result was available contacts.
The single tier-1 detection is generic and not corroborated by other high-trust engines. Widespread distribution over three years and clean sandbox verdict reduce risk, yet the unsigned status and mixed low-trust detections keep the file in the suspicious band.
What We Detected
17 of 75 engines flagged the sample; only Fortinet (tier-1) returned a named detection (W32/PossibleThreat). The remaining 15 tier-1 engines reported clean. No code signing certificate is present.
Threat Behavior
Sandbox execution produced only ambient MITRE techniques and contacted Microsoft/Akamai infrastructure plus the standard NCSI connectivity check. no complete contacted-host reputation result was available, dropped children, or persistence mechanisms were observed.
What To Do Now
Keep Windows Defender and other endpoint protection 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 tier-1 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.
- common_old prevalence (3682 sources)
- no malicious sandbox verdict
- no complete contacted-host reputation result was available
- unsigned executable
- 17 engines flagged (1 tier-1)
Treat as unverified; obtain Steam client components only from official Valve distribution channels.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete17 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 9MITRE ATT&CK techniques
- 15spawned processes
- 21network contacts
- 36filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Scans through your files and folders.
Note: Collects details about your system.
Note: Loads extra code modules while running.
Note: Connected to 20 servers during sandbox analysis.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
steamclient_loader.exe
6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
GUM7CCC.tmp
C:\Program Files\Google\Temp\GUM7CCC.tmp
04Isolated runtime analysis - Written fileObserved
GUMA43B.tmp
C:\Program Files\Google\Temp\GUMA43B.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.184.37
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.229.211.108
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 20.99.184.37
- 192.229.211.108
- 20.99.186.246
- 23.209.116.25
- 20.22.113.133
- 23.216.147.76
- 20.99.133.109
- 20.99.185.48
- a83f:8110:0:0:b00:b00:2800:1800
- a83f:8110:0:0:1b00:100:2800:0
- http://www.msftncsi.com/ncsi.txt
- C:\Program Files\Google\Temp\GUM7CCC.tmp
- C:\Program Files\Google\Temp\GUMA43B.tmp
- C:\Program Files\Google\Temp\GUMB958.tmp
- C:\Program Files\Google\Temp\GUME098.tmp
- C:\Program Files\Google\Policies
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DF.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CA.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER309.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AE5.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AF7.tmp.csv
- Global\G{C4F406E5-F024-4e3f-89A7-D5AB7663C3CD}
- Global\Common Framework RepairService Mutex
- Global\MutexRS_CLIENT_TABLE_LOCK_C__YYYIYOU_C1.DAT
- Global\MutexRS_CLIENT_TABLE_OPEN_C__YYYIYOU_C1.DAT
- Global\MutexRS_SERVER_TABLE_LOCK_C__YYYIYOU_S1.DAT
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 17 / 75engines flagged
- 3,682sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
17 of 75 antivirus engines flagged the file, including Antiy-AVL and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,682 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 12,799 times from 3,682 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: steamclient_loader.exe — 6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: GUM7CCC.tmp — C:\Program Files\Google\Temp\GUM7CCC.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: GUMA43B.tmp — C:\Program Files\Google\Temp\GUMA43B.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.229.211.108 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.99.184.37 · 192.229.211.108 · 20.99.186.246
17 of 75 engines flagged this file
View all 75 engine results
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.
Fingerprint and provenance
- File name
- steamclient_loader.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 98.5 KB
- Last analyzed
- Aug 22, 2026, 3:28 PM UTC
6d76785ff9806540c469c3b466eeacacb5d129d38723d53936a90b419f22a5a0Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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?
How do I remove 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.