File scan report
Verdict Suspicious
Is Steam
The signer has no history and the file was first seen on Aug 19, 2026.
Why Suspicious? 3 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious; isolate and analyze further before any execution on production systems.
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
3 of 69 flagged
- Flagged 3
- No detection 66
- No result 6
- Code signing Signer not verified
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The combination of a ML detection from a major antivirus engine, offensive MITRE techniques, and access to the Windows password store creates a mixed but concerning signal. The majority of major antivirus engines remained silent and no sandbox verdict was malicious, yet the unknown signer and short history (submitted shortly before Aug 22, 2026) prevent a clean classification. No external intelligence or prior similar-hash verdicts exist to resolve the ambiguity.
What We Detected
3 of the 69 antivirus engines that checked it flagged the sample. Symantec (major) returned ML.Attribute.HighConfidence; Gridinsoft labeled it Trojan.Win64.Wacatac.bot. The binary is signed by an unknown 'SteamDaddy Software Trust Authority' with no prior history.
Threat Behavior
Six files it created 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 security software enabled.
Where this verdict could be wrong2 caveats
- 15 major antivirus engines reported it clean and 1 major antivirus engine flagged it — majority of major antivirus engines did not flag.
- No sandbox returned a malicious verdict 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.
- No malicious sandbox verdict returned
- No dropped malicious files it created
- Major ML detection present
- Unknown signer with no history
- File first seen on Aug 19, 2026
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 23sandbox rule tags
- 4spawned processes
- 0network contacts
- 17filesystem & 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).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
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 5: FileSeen in the test run
SteamDaddy.exe
d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
SteamDaddy.exe
"C:\Users\<USER>\Desktop\SteamDaddy.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
powershell
"powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
sd_token.key
C:\ProgramData\SteamDaddy\sd_token.key
Test run - Evidence 5 of 5: Written fileSeen in the test run
StartupProfileData-NonInteractive
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
23MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1036
- T1047
- T1055· Process injection
- T1056· Keylogging
- T1057· Lists programs
- T1059· Runs commands
- T1059.001· Runs commands
- T1064
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1518.001· Checks your AV
- T1562· Disables security
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.003· Hides artifacts
- T1573
- T1574· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
SteamDaddy.exe"C:\Users\<USER>\Desktop\SteamDaddy.exe"powershell"powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"SteamDaddy.exe"C:\Users\user\Desktop\SteamDaddy.exe"powershell.exeC:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"
Files
16Files the file created, changed or deleted.
- Written
C:\ProgramData\SteamDaddy\sd_token.key - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive - Written
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log - Written
C:\ProgramData\SteamDaddy - Written
C:\Users\user\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_5shnxcpj.orp.psm1
Show all 16 entries for files
- Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_q4q3ilit.cw5.ps1 - Written
C:\Users\user\AppData\Roaming - Written
C:\Users\user\Documents\20260819 - Written
C:\Users\user\Documents\20260819\PowerShell_transcript.PC-XHA4722.4q4QvjAe.20260819091615.txt - Written
C:\Windows\system32\catroot - Written
C:\Windows\system32\catroot2 - Written
\Device\ConDrv\\Connect - Written
stdout - Deleted
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_5shnxcpj.orp.psm1 - Deleted
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_q4q3ilit.cw5.ps1
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
Global\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 9 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache. 5 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 1f5c8156cf07c7b10f78…368296Not checkedno saved verdict
- eb31de72690dc3041e4f…bebd56Not checkedno saved verdict
- 168561fb18f8eba8043f…740e3fNot checkedno saved verdict
- e972abc2c1baa02791ce…52e9d1Not checkedno saved verdict
- 80f6e7633d6f19baa473…fe462bNot checkedno saved verdict
Chapter 04
Technical details
3 of the 69 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- Symantec (major engine)ML.Attribute.HighConfidence
- GridinsoftTrojan.Win64.Wacatac.bot
- Trapminemalicious.moderate.ml.score
File fingerprint
- Last analyzed
- Aug 22, 2026, 9:52 PM UTC
- SHA-256
d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31- SHA-1
47f518a5ea8b2c9cda178da0d6c32659cda27aa5- MD5
9824b7882cc1171730b8f16b5a706fa1
About this file
SteamDaddy.exe is a Win32 EXE file of 17.3 MB.
- Type and size
- Win32 EXE · 17.3 MB
- Signer
- SteamDaddy Software Trust Authority (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Aug 19, 2026On VirusTotal.
- Submitted by
- 25 distinct sources
- Packer
- None detected
- Entropy
- 7.41 of 8
First scanned Updated
Antivirus consensus
3 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.
- Tier-117 engines1flagged
- Tier-235 engines1flagged
- Low-trust17 engines1flagged
View all 75 engine results
- GridinsoftMalicious: Trojan.Win64.Wacatac.bot
- SymantecMalicious: ML.Attribute.HighConfidence
- TrapmineMalicious: malicious.moderate.ml.score
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
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?
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.