File scan report
Verdict Safe
Is We
None of the 71 antivirus engines that checked it flagged this installer, though its unsigned, high-entropy code leaves some uncertainty about provenance and behavior in the test…
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
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing Unsigned
- Test run Partial
- First seen 10d ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 71 antivirus engines that checked it reported a detection, including all 17 reporting major antivirus engines. However, the executable is unsigned, and contains high-entropy code, while no sandbox run completed; obtain it only from the official distribution channel and keep security software enabled.
The strongest evidence is the complete absence of detections: none of the 71 antivirus engines that checked it flagged the executable, and all 17 reporting major antivirus engines were silent. No malware family, offensive technique, malicious child, or external-intelligence match was identified. The file is nevertheless unsigned and has only one submission on its first observed day, so its publisher and broader reputation remain unestablished. Static analysis marks the code section as high entropy and possibly packed, but identifies no packer; that feature alone does not demonstrate malware. No sandbox run completed, and no complete contacted-host reputation result is available, so runtime and network behavior cannot be characterized. The import-table fingerprint-only history is mixed and involves unrelated publishers, making it weak evidence either way.
What We Detected
None of the 71 antivirus engines that checked it flagged the executable. This includes all 17 reporting major antivirus engines, and there is no family consensus, external-intelligence hit, or known malicious file it created.
Threat Behavior
No completed sandbox run is available, so execution behavior was not observed. Four routine discovery mappings appear in the record, but without runtime coverage they do not establish hostile activity. The antivirus analysis found a high-entropy code section and marked the file as possibly packed, although no specific packer was identified and the toolchain indicates a .NET executable.
What To Do Now
The main uncertainties are provenance and freshness: the installer is unsigned and had only one submission on its first observed day. Download it only through the software publisher's official channel, verify any publisher-provided hash, and keep antivirus and security software enabled when opening it.
Where this verdict could be wrong3 caveats
- The executable is unsigned and was observed only once on its first day, leaving its claimed origin unverified.
- High-entropy executable code suggests compression or obfuscation, although no specific packer was identified.
- No sandbox run completed, so the absence of runtime findings does not establish normal behavior.
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 71 antivirus engines that checked it reported a detection.
- All 17 reporting major antivirus engines returned no detection.
- No malware-specific researcher rules or external threat-feed matches were found.
- No offensive behavior mappings or known malicious dropped files were identified.
- The Windows executable has no authenticated publisher signature.
- It was and had only one submission, so reputation is not yet established.
- The code section has high entropy and may be compressed or obfuscated.
- No completed sandbox run is available to confirm behavior in the test run.
6 sources checked · 4 complete · 1 partial · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 partial · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 15, 2026, 7:41 PM UTC
- SHA-256
786f34335aea9663c14c629cd5eb26fd5ccbbc94f6cc5216701f5e73e6e2b7c5- SHA-1
f07b00a10cf2fdb7c3d65673d0fc5e79d6fbe105- MD5
2ee5ecdb479d45d9d60f646b45b63261
About this file
WeMod Outriders Setup.exe is a Win32 EXE file of 160.6 kB.
- Type and size
- Win32 EXE · 160.6 kB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 15, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 7.34 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 04
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is WeMod Outriders Setup.exe safe?
What is WeMod Outriders Setup.exe?
How many antivirus engines detected WeMod Outriders Setup.exe?
What is the SHA-256 hash of WeMod Outriders Setup.exe?
Is it safe to install WeMod Outriders Setup.exe?
How up to date is this analysis of WeMod Outriders Setup.exe?
Community
Member reviews and reports for this exact file hash.