File scan report

Verdict Suspicious

Analyzed , 2 months ago

Is SteamDaddy.exe safe? Treat it as suspicious.

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.

Don't run it until you know where it came from

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

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

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
FileSteamDaddy.exe17.3 MBSHA-256 d64a1fce5248…550a31
  • Code signing Signer not verified
  • Test run Completed
  • First seen 2mo ago
3 of the 69 antivirus engines that checked it flag it, including Symantec (Norton) and Gridinsoft.

Chapter 02

Why we think so

3 points against it and 2 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

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.

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.

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.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 5: FileSeen in the test run

      SteamDaddy.exe

      d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 5: ProcessSeen in the test run

      SteamDaddy.exe

      "C:\Users\<USER>\Desktop\SteamDaddy.exe"

      Test run
    2. Evidence 3 of 5: ProcessSeen in the test run

      powershell

      "powershell" -NoProfile -Command "(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID"

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 5: Written fileSeen in the test run

      sd_token.key

      C:\ProgramData\SteamDaddy\sd_token.key

      Test run
    2. Evidence 5 of 5: Written fileSeen in the test run

      StartupProfileData-NonInteractive

      C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive

      Test run
    3. +1 more recorded observation

5 facts from the test run. See the full activity list.

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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 3 of 69 engines flagged it · 6 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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

Chapter 05

Questions & answers

Short answers to the 7 questions people ask most about this file.

Is SteamDaddy.exe safe, or is it malware?
SteamDaddy.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 3 of the 69 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is SteamDaddy.exe?
SteamDaddy.exe is a Windows program, about 17.3 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Aug 19, 2026.
How many antivirus engines detected SteamDaddy.exe?
3 of the 69 antivirus engines that checked it flag SteamDaddy.exe, including Symantec (Norton) and Gridinsoft. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran SteamDaddy.exe — what should I do?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
Is SteamDaddy.exe digitally signed?
It carries a signature in the name of SteamDaddy Software Trust Authority that could not be verified. Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
What is the SHA-256 hash of SteamDaddy.exe?
The SHA-256 fingerprint of SteamDaddy.exe is d64a1fce524835c78d2e712f85d7512fda94ccb840e64ccd6f7580ac61550a31, and its MD5 is 9824b7882cc1171730b8f16b5a706fa1. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of SteamDaddy.exe?
This report reflects the scan on Aug 22, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Other files people checked with the same name, and recent reports with the same rating. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.