File scan report
Verdict Suspicious
Is Orchard Setup. exe safe? Treat it as suspicious.
This unsigned, recently seen installer drew 5 of 75 generic machine-learning detections while sandbox runs showed ordinary setup activity, leaving too little evidence for a firm…
Read the whole reasonShow less
Why Suspicious? 5 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
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
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
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
5 of 68 flagged
- Flagged 5
- No detection 63
- No result 7
- Code signing Unsigned
- Test run Completed
- First seen 8d ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
5 of the 68 antivirus engines that checked it flagged this installer, all with generic or machine-learning labels, and only one major antivirus engine (Sophos, as a possible unwanted program) among them. Sandbox runs showed normal installer actions and no high-risk techniques. However, the file is unsigned and only days old, so nothing confirms who published it.
Detections are few and generic: Sophos labels the file a machine-learning possible unwanted program, and CrowdStrike, Sangfor, APEX and Trapmine add low-confidence or rule labels without naming a malware family. Seventeen other major antivirus engines did not flag it. Six sandbox runs recorded a standard installer flow: it unpacks temporary files, launches a bootstrapper, registers an uninstall entry and downloads content from its own update host. Neither host contacted is known to be malicious in our records. The file has no digital signature and no publisher history, and earlier files sharing its build fingerprint come from unrelated publishers, so nothing positively vouches for it.
What We Detected
5 of the 68 antivirus engines that checked it flagged this file. Sophos was the only major antivirus engine, with a machine-learning label for a possible unwanted program. CrowdStrike, Sangfor, APEX and Trapmine used generic or low-confidence labels, and no malware family was named. The installer has no digital signature.
Threat Behavior
Across six sandbox runs, the installer extracted temporary setup files and started a bootstrapper with installation arguments. It wrote an uninstall registry entry and downloaded several content objects from its own update server. No high-risk techniques, injected processes or persistence beyond the uninstall entry were observed. Neither contacted host is known to be malicious in our records.
What To Do Now
Only run this installer if you obtained it from the developer's official site and trust that source. If in doubt, wait for wider adoption or a signed release, and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- The installer behaviour seen in the sandbox (temporary installer files, an uninstall entry, a bootstrapper downloading content) looks like ordinary software setup, and the flagging engines use only generic machine-learning labels.
- The installer downloads further content at run time, and that downloaded content was not judged in this scan.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No major antivirus engines named a malware family, and 17 of them did not flag it.
- Sandbox runs showed ordinary installer activity with no high-risk techniques.
- Neither contacted host is known to be malicious in our records.
- The installer has no digital signature, so its publisher cannot be confirmed.
- The file was first seen only days ago.
- Sophos flagged it as a possible unwanted program, and four other engines used generic labels.
- It downloads additional content from the internet during installation.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 6 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 6isolated sandbox runs
- 23sandbox rule tags
- 3spawned processes
- 2network contacts
- 31filesystem & 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.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
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.
Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
OrchardSetup.exe
37398cbdfa9f17961a68adf13545122ad5875edb418b316f3f972ba5eae60a4d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
OrchardSetup.exe
"C:\Users\<USER>\Desktop\OrchardSetup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
OrchardBootstrapper.exe
"C:\Users\<USER>\AppData\Local\Temp\nspB0E3.tmp\OrchardBootstrapper.exe" --install --no-launch --channel canary
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
nszB084.tmp
C:\Users\<USER>\AppData\Local\Temp\nszB084.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
modern-wizard.bmp
C:\Users\<USER>\AppData\Local\Temp\nspB0E3.tmp\modern-wizard.bmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
depot.sfg545.dev
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
104.21.71.145
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 23 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
5 of the 68 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.
Engines that flagged it 5
- Sophos (major engine)Generic ML PUA (PUA)
- APEXMalicious
- CrowdStrikewin/malicious_confidence_60% (D)
- SangforTrojan.Win32.Save.a
- Trapminesuspicious.low.ml.score
File fingerprint
- Last analyzed
- Oct 22, 2026, 2:15 PM UTC
- SHA-256
37398cbdfa9f17961a68adf13545122ad5875edb418b316f3f972ba5eae60a4d- SHA-1
640acea0266310d9da14e91603a72bf975e60771- MD5
0ee2c820bfb9c97b40c9630b089db8c0
About this file
OrchardSetup.exe is a Win32 EXE file of 457.1 kB.
- Claims to be
- Orchard setup (Orchard)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 457.1 kB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 17, 2026On VirusTotal.
- Submitted by
- 30 distinct sources
- Packer
- None detected
- Entropy
- 6.09 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 OrchardSetup.exe safe, or is it malware?
What is OrchardSetup.exe?
How many antivirus engines detected OrchardSetup.exe?
I already downloaded and ran OrchardSetup.exe — what should I do?
What is the SHA-256 hash of OrchardSetup.exe?
How up to date is this analysis of OrchardSetup.exe?
Community
Member reviews and reports for this exact file hash.