MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 1 month ago

Is saya.exe safe? Treat it as suspicious.

Long history and lack of major or sandbox malicious verdicts keep the risk moderate.

Why Suspicious? 2 antivirus engines flag it, but no major engine agrees; 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; do not execute on production systems until additional dynamic analysis or a signed vendor update is available.

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.

Why we think so

Share this file report

saya.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

2 of 71 flagged

  • Flagged 2
  • No detection 69
  • No result 4
Filesaya.exe1.1 MBSHA-256 903f298556f4…2105c2
  • Code signing Unsigned
  • Test run Completed
  • First seen 13y ago
2 of the 71 antivirus engines that checked it flag it, including APEX and Trapmine.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The engine profile matches the classic less reliable-only false-positive pattern, yet the unsigned status and confirmed activity prevent a clean classification. No major antivirus engines or external-intel source corroborates malice, and prevalence data indicate the file has circulated for over a decade. Because contacted-host reputation data are missing, the direct-IP traffic cannot be dismissed. The combination of static, behavioural, and coverage gaps produces a borderline mixed-signal assessment.

Where this verdict could be wrong1 caveat
  • communityComments[0] reports FileScan.IO verdict 'SUSPICIOUS' with 100/100 confidence, but this is a single third-party annotation without major corroboration.

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 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
  • 14sandbox rule tags
  • 2spawned processes
  • 2network 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).

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

  • Note: Listed the programs running on the test computer.

  • Note: Talked to servers over the internet during the test run.

  • 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).

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.

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 7: FileSeen in the test run

      saya.exe

      903f298556f45174ea2dbeaf4a0aebe2986a54a47082fa2dbc4b14af672105c2

      Uploaded file

  2. Processes

    What ran

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

      saya.exe

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

      903f298556f45174ea2dbeaf4a0aebe2986a54a47082fa2dbc4b14af672105c2.exe

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

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

      WER9066.tmp

      C:\ProgramData\Microsoft\Windows\WER\Temp\WER9066.tmp

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

      WER9066.tmp.csv

      C:\ProgramData\Microsoft\Windows\WER\Temp\WER9066.tmp.csv

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      209.197.3.8

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      20.22.113.133

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

2 of the 71 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 2 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial2 hosts contacted in the test run had no completed reputation check Details for contacted hosts
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 2

  • APEXMalicious
  • Trapminemalicious.moderate.ml.score

File fingerprint

Last analyzed
Sep 6, 2026, 1:17 PM UTC
SHA-256
903f298556f45174ea2dbeaf4a0aebe2986a54a47082fa2dbc4b14af672105c2
SHA-1
637a89b96dd8159fe3c689324669a6f33cbcec9b
MD5
a49b59f11016e157684cbb44c77dcbf6

About this file

saya.exe is a Win32 EXE file of 1.1 MB.

Type and size
Win32 EXE · 1.1 MB
Signer
UnsignedNo code signature.
First seen
May 14, 2013On VirusTotal.
Submitted by
432 distinct sources
Packer
None detected
Entropy
6.63 of 8

First scanned

Chapter 05

Questions & answers

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

Is saya.exe safe, or is it malware?
saya.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 2 of the 71 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 saya.exe?
saya.exe is a Windows program, about 1.1 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on May 14, 2013.
How many antivirus engines detected saya.exe?
2 of the 71 antivirus engines that checked it flag saya.exe, including APEX and Trapmine. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran saya.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.
What is the SHA-256 hash of saya.exe?
The SHA-256 fingerprint of saya.exe is 903f298556f45174ea2dbeaf4a0aebe2986a54a47082fa2dbc4b14af672105c2, and its MD5 is a49b59f11016e157684cbb44c77dcbf6. 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 saya.exe?
This report reflects the scan on Sep 6, 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.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
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.