File scan report
Verdict Safe
Is Omni
No antivirus engine detected a threat, and the completed sandbox run showed installer activity without corroborating destructive behavior or hostile network reputation.
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 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 16d 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 flagged this installer, including all 17 major contributors, and its completed sandbox run did not issue a malware finding. It is unsigned and recently observed, while three offensive technique mappings deserve caution, but no engine, host-reputation, packing, or external-intelligence evidence corroborates them.
None of the 70 antivirus engines that checked it flagged the executable, and all 17 major contributors reported no detection. One completed sandbox run recorded installation files, uninstall entries, a custom URL protocol, and browser-extension resources without issuing a malware finding. The T1134, T1485, and mappings are meaningful counter-signals, but the evidence does not show destructive results, injected processes, or persistence indicators. Reputation checks covered the distinct observed hosts and found no malicious or suspicious entries; one listed IP and its associated domain were identified as sandbox background traffic. The file is unsigned and recently observed, which limits provenance confidence, but it is not packed and has no brand mismatch or malware-specific external-intelligence hits. Similar-file history is mixed and weak because every match is based only on an import-table fingerprint shared across unrelated installers.
What We Detected
None of the 70 antivirus engines that checked it flagged the file, including all 17 major contributors. No malware family was identified, and researcher intelligence produced no malware-specific YARA, MalwareBazaar, or CIRCL match.
Threat Behavior
One completed sandbox run observed behavior consistent with an installer: it wrote the main application, browser-extension resources, uninstall information, and a custom URL-protocol registration. The analysis mapped T1134, T1485, and T1486, which merit caution, but it did not record injected processes, persistence indicators, destructive outcomes, or a malicious sandbox conclusion. Reputation coverage included the distinct observed hosts and found no known malicious or suspicious entries; documented analysis-environment contacts were excluded from the sample's activity.
What To Do Now
The main limitation is provenance: this recently observed Windows executable is unsigned and has no established publisher history. Obtain it from the developer's official release channel, verify the SHA-256 value before running it, and keep security software enabled. If the source cannot be verified, avoid installation despite the favorable scan evidence.
Where this verdict could be wrong2 caveats
- The executable is unsigned and only five days old, so its publisher and release provenance cannot be authenticated.
- The sandbox mapped T1134, T1485, and T1486; these are concerning capability labels, although no destructive outcome or malicious sandbox verdict corroborated them.
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 contributors.
- The completed sandbox run did not return a malware finding and primarily showed expected installer activity.
- The observed hosts covered by reputation checks had no known malicious or suspicious entries.
- No high-entropy code, likely packing, packer identification, brand mismatch, or malware-specific research rule was found.
- The Windows executable is unsigned, so its publisher and integrity are not authenticated through a code-signing certificate.
- The file was first observed on Oct 10, 2026 and has only moderate submission history.
- The sandbox assigned three offensive-technique mappings associated with token manipulation and destructive impact, although it did not confirm those outcomes.
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- 25sandbox rule tags
- 2spawned processes
- 0network contacts
- 22filesystem & mutex artifacts
Includes the sandbox verdicts, 25 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 15, 2026, 8:39 AM UTC
- SHA-256
3cc2c1f6bd68175108a25d6f0b6de6a75d1e572a1fef9a6631e2ca344ffb6869- SHA-1
955a0c528abf6098c19fed41729107212878f637- MD5
7913448fd57eae5ba833882fc960097b
About this file
OmniGet_0.12.0_x64-setup.exe is a Win32 EXE file of 41.3 MB.
- Type and size
- Win32 EXE · 41.3 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 10, 2026On VirusTotal.
- Submitted by
- 10 distinct sources
- Packer
- None detected
- Entropy
- 6.04 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 OmniGet_0.12.0_x64-setup.exe safe?
What is OmniGet_0.12.0_x64-setup.exe?
How many antivirus engines detected OmniGet_0.12.0_x64-setup.exe?
What is the SHA-256 hash of OmniGet_0.12.0_x64-setup.exe?
Is it safe to install OmniGet_0.12.0_x64-setup.exe?
How up to date is this analysis of OmniGet_0.12.0_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.