Is SteamDaddy.exe safe?
Three engines flag the file, one tier-1, while sandbox shows process-injection and LSASS access.
One tier-1 engine and two others detect malicious attributes; sandbox observed PowerShell, process injection, and LSASS access. The signer has no history and the file is only three days old.
d64a1fce524835c78d…7580ac61550a31Recommended 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 and two others detect malicious attributes; sandbox observed PowerShell, process injection, and LSASS access. The signer has no history and the file is only three days old.
The combination of a tier-1 ML detection, offensive MITRE techniques, and LSASS access creates a mixed but concerning signal. The majority of tier-1 engines remained silent and no sandbox verdict was malicious, yet the unknown signer and recent submission prevent a clean classification. No external intelligence or prior similar-hash verdicts exist to resolve the ambiguity.
What We Detected
3 of 75 engines flagged the sample. Symantec (tier-1) returned ML.Attribute.HighConfidence; Gridinsoft labeled it Trojan.Win64.Wacatac.bot. Sandbox execution recorded PowerShell commands, process-injection attempts (T1055), and LSASS memory access (T1056). The binary is signed by an unknown 'SteamDaddy Software Trust Authority' with no prior history.
Threat Behavior
Offensive techniques observed include impairing defenses (T1562.001) and credential-store interaction. Six child files were dropped, none flagged malicious by our cache. no complete contacted-host reputation result was available or external-intel hits were recorded.
What To Do Now
Do not execute the file. Keep endpoint protection enabled. If the file is required, run it only in an isolated virtual machine and monitor for LSASS or PowerShell anomalies.
Where this verdict could be wrong2 caveats
- engines.tier1ReportedClean=15 and tier1Malicious=1 — majority of high-trust engines did not flag.
- behaviour.hasMaliciousSandboxVerdict=false despite offensive MITRE techniques observed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 tier-1 engines reported clean
- No malicious sandbox verdict returned
- No dropped malicious children
- Tier-1 ML detection present
- Sandbox observed LSASS access
- Unknown signer with no history
- File first seen 3 days ago
Treat as suspicious; isolate and analyze further before any execution on production systems.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules 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
- 23MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 17filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
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: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
SteamDaddy.exe
d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\SteamDaddy.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
sd_token.key
C:\ProgramData\SteamDaddy\sd_token.key
04Isolated runtime analysis - Written fileObserved
StartupProfileData-NonInteractive
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\ProgramData\SteamDaddy\sd_token.key
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log
- C:\ProgramData\SteamDaddy
- C:\Users\user\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
- C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_5shnxcpj.orp.psm1
- C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_q4q3ilit.cw5.ps1
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- 1f5c8156cf07c7b10f78…368296Never scannednever seen before
- eb31de72690dc3041e4f…bebd56Never scannednever seen before
- 168561fb18f8eba8043f…740e3fNever scannednever seen before
- e972abc2c1baa02791ce…52e9d1Never scannednever seen before
- 80f6e7633d6f19baa473…fe462bNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 3 / 75engines flagged
- 25sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Gridinsoft and Symantec.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 27 times from 25 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: SteamDaddy.exe — d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\SteamDaddy.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: sd_token.key — C:\ProgramData\SteamDaddy\sd_token.key
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: StartupProfileData-NonInteractive — C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
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 saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
3 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- SteamDaddy.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: SteamDaddy Software Trust Authority
- Size
- 16.5 MB
- Last analyzed
- Aug 22, 2026, 9:52 PM UTC
d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31Safety & 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 SteamDaddy.exe safe, or is it malware?
What is SteamDaddy.exe?
How many antivirus engines detected SteamDaddy.exe?
I already downloaded and ran SteamDaddy.exe — what should I do?
How do I remove SteamDaddy.exe?
What kind of malware is SteamDaddy.exe?
Is SteamDaddy.exe digitally signed?
What is the SHA-256 hash of SteamDaddy.exe?
How up to date is this analysis of SteamDaddy.exe?
Community
Member reviews and reports for this exact file hash.