File scan report
Verdict Safe
Is project-
None of the 69 antivirus engines that checked it flagged the executable, and its completed sandbox run returned clean, though its unsigned, status warrants source verification.
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.
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
0 of 69 flagged
- Flagged 0
- No detection 69
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 16d 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
None of the 69 antivirus engines that checked it reported a detection, including all reporting major antivirus engines, and the completed sandbox run returned clean. The unsigned executable is and carries unconfirmed and mappings, so obtain it only from the expected project source and keep security software enabled.
No antivirus engine among the 75 returned a malicious or suspicious result, and there is no family consensus. One completed sandbox run returned clean and showed no network contacts, persistence indicators, or named injected process. The and mappings are cautionary, but the saved evidence does not prove an injection target or malicious intent. The antivirus analysis found neither high-entropy code nor an identified packer. Confidence is moderated because the executable is unsigned, and six dropped files lack saved verdicts; additionally, no complete contacted-host reputation result is available.
What We Detected
None of the 69 antivirus engines that checked it flagged the executable, including the reporting major antivirus engines. No named malware family, hacking tool label, external research rule, packing indicator, or malicious child verdict was present.
Threat Behavior
One completed sandbox run returned clean. The run recorded no sample network contacts or persistence indicators. Six dropped files have no saved verdicts, so their status remains unresolved, and no complete contacted-host reputation result is available.
What To Do Now
Confirm the file came from the expected project or developer because it is unsigned and newly observed. Keep antivirus and security software enabled, and rescan after reputation has had time to develop if the source cannot be independently verified.
Where this verdict could be wrong3 caveats
- The executable is unsigned and so its publisher and longer-term reputation are not established.
- The sandbox mapped possible process injection and privilege escalation, although it identified no injected process and returned a clean verdict.
- Six dropped files lack saved verdicts, and no complete contacted-host reputation result is available.
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 69 antivirus engines that checked it flagged the file.
- The completed sandbox run returned clean.
- No persistence indicators or sample network contacts were recorded during the run.
- The antivirus analysis found no packer or high-entropy code.
- No malicious file it created was identified among the inspected files.
- The Windows executable is unsigned, leaving no verified publisher identity.
- It was first observed very recently, so long-term reputation is limited.
- The sandbox mapped possible process injection and privilege escalation, without identifying an injection target.
- Six dropped files do not yet have saved verdicts.
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 our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 13sandbox rule tags
- 2spawned processes
- 0network contacts
- 20filesystem & mutex artifacts
Includes the sandbox verdicts, 13 mapped techniques, every process, file, registry and network entry and 6 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 69 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.
File fingerprint
- Last analyzed
- Oct 10, 2026, 7:12 PM UTC
- SHA-256
db92d82f489e59a9edf078c738e37916316658690c817754a108c6c7d64a9acf- SHA-1
11d0fcaa3d9e5c7e992860e192a7336eeccfcc54- MD5
ffbaf84ed8e1694d20d7a80e93d7a82c
About this file
project-reclaimer.exe is a Win32 EXE file of 36.8 MB.
- Type and size
- Win32 EXE · 36.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 10, 2026On VirusTotal.
- Submitted by
- 13 distinct sources
- Packer
- None detected
- Entropy
- 6.26 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 project-reclaimer.exe safe?
What is project-reclaimer.exe?
How many antivirus engines detected project-reclaimer.exe?
What is the SHA-256 hash of project-reclaimer.exe?
Is it safe to run project-reclaimer.exe?
How up to date is this analysis of project-reclaimer.exe?
Community
Member reviews and reports for this exact file hash.