File scan report
Verdict Safe
Is SPFL27_
Only 2 of the 70 antivirus engines that checked it raised generic alerts, while broad distribution and clean combined sandbox results strongly indicate false-positive detections.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Install 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
2 of 70 flagged
- Flagged 2
- No detection 68
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 6d ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The two generic detections are not corroborated by any major antivirus engine, named malware family, malicious runtime result, or threat-intelligence match. The installer has been submitted by 113 distinct sources, and the sandbox runs produced a combined clean verdict without recorded injection targets or sample network contacts.
Only 2 of the 70 antivirus engines that checked it flagged the executable, and none of the major antivirus engines detected it. Both alerts are generic, with one focused on obfuscation rather than a named malware family. The file has been submitted by 113 distinct sources, providing a meaningful benign anchor. The combined sandbox verdict was clean, with no high-risk techniques, named injection target, persistence indicator, or sample network contact recorded. .NET Reactor protection and the lack of a digital signature warrant some caution, but they do not outweigh the broader evidence that the two detections are false positives.
What We Detected
Two of the 70 antivirus engines that checked it flagged the executable. APEX used a generic malicious label, while Skyhigh reported behavior resembling an obfuscated Windows program; no major antivirus engines identified malware, and no real malware family was named.
Threat Behavior
The sandbox runs produced a combined clean verdict. No high-risk technique or named process-injection target was recorded, and the T1055 mapping lacked the artifact needed to establish injection. The sample made no recorded network contacts. The executable uses .NET Reactor protection, which can account for generic obfuscation alerts but makes manual inspection more difficult.
What To Do Now
Use the installer only if it came from the expected official distribution channel, and keep security software enabled. If its source cannot be verified, obtain a fresh copy from the publisher rather than relying on this executable.
Where this verdict could be wrong3 caveats
- Two engines flagged the executable, including Skyhigh with a behavior-based obfuscation label.
- The executable is unsigned and protected with .NET Reactor, reducing transparency into its code.
- No complete contacted-host reputation result is available, although the sandbox runs recorded no sample network contacts.
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 major antivirus engines flagged the file.
- The file was submitted by 113 distinct sources across 133 submissions.
- The combined sandbox verdict was clean, with no named injection target or high-risk technique recorded.
- No malware-specific community rules or public malware-sample database entry matched the hash.
- No inspected file it created was identified as harmful.
- Two antivirus engines raised generic alerts.
- The executable is unsigned.
- The program is protected with .NET Reactor, which obscures its code.
- No complete reputation check was available for contacted hosts.
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 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 11sandbox rule tags
- 6spawned processes
- 0network contacts
- 20filesystem & mutex artifacts
Includes the sandbox verdicts, 11 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
2 of the 70 antivirus engines that checked it flag it; no publisher signature.
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 2
The Safe verdict weighed these detections and treats them as non-decisive.
- APEXMalicious
- SkyhighBehavesLike.Win32.ObfuscatedPoly.rh
File fingerprint
- Last analyzed
- Nov 7, 2026, 10:35 AM UTC
- SHA-256
b23feb646fa8d049221ff9fbb13a6192d05161e21516470eaabcb03b73a7c8de- SHA-1
05464c738f669ef7cd072a43af70addeec95f8e4- MD5
72a3699857a19674dbbc563206508a97
About this file
SPFL27_setup.exe says it is SP Football Life 2027 Setup (SP Football Life 2027), 5.0 MB.
- Claims to be
- SP Football Life 2027 Setup (SP Football Life 2027)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 5.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 31, 2026On VirusTotal.
- Submitted by
- 113 distinct sources
- Packer
- .NET Reactor 2.X-3.X (DetectItEasy protector)Packing hides code; legitimate installers use it too.
- Entropy
- 6.36 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, 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 SPFL27_setup.exe safe?
What is SPFL27_setup.exe?
How many antivirus engines detected SPFL27_setup.exe?
What is the SHA-256 hash of SPFL27_setup.exe?
Is it safe to install SPFL27_setup.exe?
How up to date is this analysis of SPFL27_setup.exe?
Community
Member reviews and reports for this exact file hash.