File scan report
Verdict Safe
Is Reg
One of the 71 antivirus engines that checked it raised a generic alert, while long-term prevalence, major silence, and the absence of corroborating hostile activity support a…
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 71 flagged
- Flagged 1
- No detection 70
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 15y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
SentinelOne alone flagged the executable with a generic suspicious-file label; none of the 18 major antivirus engines detected it. The file has been submitted by 137 sources since it was first seen on Jun 9, 2011, and the sandbox summary recorded no corroborated high-risk technique or named injection target.
Only 1 of the 71 antivirus engines that checked it flagged the file, and the label is generic rather than a named malware family. All 18 major antivirus engines were silent, which weighs strongly against the isolated alert. The file also has substantial history: 137 distinct sources submitted it 150 times after it was first seen on Jun 9, 2011. No malware-specific community rule, public sample-database entry, malicious child, packing indicator, or brand mismatch corroborates the detection. The executable is unsigned and a complete contacted-address reputation result is unavailable, but these limitations do not outweigh the broad benign evidence.
What We Detected
SentinelOne was the only engine to flag the file, using a generic suspicious-PE label. None of the 18 major antivirus engines detected it, and no engine identified a real malware family.
Threat Behavior
The sandbox summary included mappings associated with process injection and defence impairment, but it recorded neither a named injection target nor an artefact demonstrating those actions. No corroborated high-risk technique, malicious dropped file, persistence indicator, or sample-originated domain contact was identified. A complete reputation result for every contacted address was not available.
What To Do Now
The isolated generic detection is most consistent with a false positive, particularly given 137 distinct submitters and a history dating to Jun 9, 2011. Keep security software enabled and obtain the executable from its expected source before running it; if its origin is unclear, verify its hash with the distributor.
Where this verdict could be wrong3 caveats
- SentinelOne reports a generic suspicious-PE detection.
- The executable is unsigned, so there is no verified publisher identity anchoring it.
- A complete reputation check was not available for every contacted address.
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 18 major antivirus engines detected the file.
- The file has been submitted by 137 distinct sources and was first seen on Jun 9, 2011.
- The sandbox summary recorded no named process-injection target or corroborated high-risk technique.
- No malware-specific community rules or public malware-sample listing matched the hash.
- The executable does not appear packed and contains no high-entropy code section.
- The executable has no verified digital signature.
- SentinelOne reports a generic suspicious-file detection.
- A complete reputation check was unavailable for every contacted address.
6 sources checked · 5 complete · 1 partial. 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- 11sandbox rule tags
- 2spawned processes
- 4network contacts
- 24filesystem & mutex artifacts
Includes 11 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
1 of the 71 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
The Safe verdict weighed these detections and treats them as non-decisive.
- SentinelOneStatic AI - Suspicious PE
File fingerprint
- Last analyzed
- May 22, 2026, 11:03 AM UTC
- SHA-256
1284106bcfc820bc983810a3bacbfc8f3db96af945013642a6078e594cfd076b- SHA-1
2e210eb46ec87c901205d9bf818de13f25b10f1d- MD5
31d2286967caddc168b2a08845cd36ad
About this file
RegOwnit.exe is a Win32 EXE file of 3.8 MB.
- Type and size
- Win32 EXE · 3.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 9, 2011On VirusTotal.
- Submitted by
- 137 distinct sources
- Packer
- None detected
- Entropy
- 6.07 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
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 RegOwnit.exe safe?
What is RegOwnit.exe?
How many antivirus engines detected RegOwnit.exe?
What is the SHA-256 hash of RegOwnit.exe?
Is it safe to run RegOwnit.exe?
How up to date is this analysis of RegOwnit.exe?
Community
Member reviews and reports for this exact file hash.