File scan report
Verdict Safe
Is SAFlash
None of the 70 antivirus engines that checked it flagged this widely circulated Flash Player projector-style executable, seen by nearly 1,900 submitters since 2018, though it…
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
The file shows no signs of malware, but because it is unsigned and Flash-based, run it only if it came from a source you trust, and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 7y ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 70 antivirus engines that checked it in our network flagged this file, including all 17 major antivirus engines. It has circulated since 2018 among almost 1,900 submitters. Its one sandbox run was clean, writing only Flash Player settings and opening a web page in Chrome. It is unsigned, so its publisher cannot be verified.
The file is old and widely seen, with 1,884 unique submitters over roughly eight years, which is typical of commodity software. The single sandbox run was clean: the file wrote Flash Player settings and cache files and launched Chrome to a GitHub Pages site. One mapped data-destruction technique appeared without any matching destructive activity. All 36 contacted hosts we checked have no malicious or suspicious record, and no external malware intelligence matched. The lack of a code signature is the main caveat.
What We Detected
None of the 70 antivirus engines that checked it flagged this file, and all 17 major antivirus engines reported it undetected. It has no matches in external malware intelligence feeds or YARA rule sets. It has been in circulation since November 2018, with 1,884 unique submitters. The executable is not digitally signed.
Threat Behavior
One sandbox run completed with a clean result. The program wrote Flash Player shared-object and settings files under the user's roaming profile. It opened Chrome to a GitHub Pages address and contacted ordinary Google, Microsoft and GitHub infrastructure. All 36 contacted hosts we cross-checked have no malicious or suspicious record. One data-destruction technique was mapped, but no deletion or wiping activity was recorded. The ten dropped files have no saved verdicts, which leaves that coverage incomplete rather than negative.
What To Do Now
The evidence fits a standalone Flash projector-style application. Adobe Flash itself is end-of-life and no longer receives security updates, so run such content only if you trust its source. Keep your antivirus enabled.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so no publisher identity can be confirmed.
- One sandbox run mapped a data-destruction technique and recorded activity in Google updater processes, though no destructive file activity or malicious verdict accompanied it.
- The file tags include a Tor-related network tag, which was not corroborated by any flagged host.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged the file, including all 17 major antivirus engines.
- It has been widely seen since 2018, with nearly 1,900 unique submitters.
- The sandbox run was clean and wrote only Flash Player settings and cache files.
- None of the hosts it contacted have a malicious or suspicious record.
- The executable has no digital signature, so the publisher cannot be verified.
- It is based on Adobe Flash Player technology, which is end-of-life and unpatched.
- Files it dropped during analysis have no saved verdicts yet.
6 sources checked · all complete. 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- 9sandbox rule tags
- 11spawned processes
- 17network contacts
- 40filesystem & mutex artifacts
Includes the sandbox verdicts, 9 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 16, 2026, 9:20 PM UTC
- SHA-256
eb84edd6bc07dbbe12f835883689e01398b3c36bb49261a69ed9cde8e1e38eb5- SHA-1
ab0fa013436603aa6a289631af3408b0ccf68aec- MD5
9e75ccec9f6710d2f246966cd95a48ff
About this file
SAFlashPlayer.exe is a Win32 EXE file of 53.1 MB.
- Type and size
- Win32 EXE · 53.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Nov 21, 2018On VirusTotal.
- Submitted by
- 1,884 distinct sources
- Packer
- None detected
- Entropy
- 6.74 of 8
First scanned
Includes every engine result (75), PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is SAFlashPlayer.exe safe?
What is SAFlashPlayer.exe?
How many antivirus engines detected SAFlashPlayer.exe?
What is the SHA-256 hash of SAFlashPlayer.exe?
Is it safe to run SAFlashPlayer.exe?
How up to date is this analysis of SAFlashPlayer.exe?
Community
Member reviews and reports for this exact file hash.