File scan report
Verdict Safe
Is Readest_
None of the 65 antivirus engines that checked it flagged this installer, and its completed sandbox run produced no malicious verdict or independently attributable network activity.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Unsigned
- Test run Completed
- First seen 21d 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 65 antivirus engines that checked it flagged the executable, including the reporting major antivirus engines. One sandbox run produced no malicious verdict, while its recorded contacts were identified as analysis-environment background traffic; however, the file is unsigned and four dropped components remain unclassified.
The strongest evidence is the complete absence of detections: none of the 65 antivirus engines that checked it flagged the file, and there is no named threat family. One completed sandbox run returned no malicious verdict, and the listed network contacts were attributed to the analysis environment rather than the sample. Static PE evidence found neither high-entropy code nor a recognized packer. is a cautionary behavior mapping, but it lacks corroboration from process injection, hostile network activity, malicious files it created, or antivirus detections. The unsigned signature state and recent first observation lower assurance, while the similar-file history is weak because every match is an import-table fingerprint-only installer-framework collision.
What We Detected
None of the 65 antivirus engines that checked it flagged the executable, and no engine supplied a malware-family label. Static PE analysis found no recognized packer, no likely packing, and no high-entropy code.
Threat Behavior
One completed sandbox run produced no malicious verdict. It mapped T1134, which can describe token manipulation, but there was no recorded process injection or other offensive behavior to corroborate abuse. All listed network contacts were identified as background traffic from the analysis environment, not sample-attributable communication. Four dropped installer components remain unclassified because no saved verdict exists for them.
What To Do Now
The evidence supports ordinary installer activity, but the executable has no verified publisher signature and was first observed on Oct 5, 2026. Obtain it from the project's official release channel, verify the SHA-256 value, and keep security software enabled while installing.
Where this verdict could be wrong3 caveats
- The executable is unsigned and recently observed, so its publisher identity cannot be authenticated.
- The token-manipulation mapping can be associated with privilege abuse, although no malicious sandbox verdict or supporting process-injection evidence was recorded.
- Four dropped files have no saved classification, leaving incomplete coverage of installer components.
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 65 antivirus engines that checked it flagged the file.
- The completed sandbox run produced no malicious verdict.
- The recorded network contacts were analysis-environment background traffic rather than sample activity.
- The antivirus analysis found no packing or high-entropy code.
- No malicious file it created was identified.
- The executable is unsigned, so its publisher identity and integrity are not authenticated by a code-signing certificate.
- It was first observed on Oct 5, 2026, providing limited reputation history.
- The sandbox mapped token manipulation behavior, though it found no corroborating process injection.
- Four dropped installer components do not yet have saved classifications.
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- 19sandbox rule tags
- 1spawned processes
- 0network contacts
- 19filesystem & mutex artifacts
Includes the sandbox verdicts, 19 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
None of the 65 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 10, 2026, 10:42 AM UTC
- SHA-256
ad534a31239b651342a484e1af2c9d1038644143f26ca9eb3891a7d94b15a6c5- SHA-1
18053be60aad983963e814ec99359bb2e9f77a6a- MD5
db09621166fdd6da8c175fd2d4a90bcf
About this file
Readest_0.12.12_x64-setup.exe is a Win32 EXE file of 57.9 MB.
- Type and size
- Win32 EXE · 57.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 5, 2026On VirusTotal.
- Submitted by
- 43 distinct sources
- Packer
- None detected
- Entropy
- 6.05 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 Readest_0.12.12_x64-setup.exe safe?
What is Readest_0.12.12_x64-setup.exe?
How many antivirus engines detected Readest_0.12.12_x64-setup.exe?
What is the SHA-256 hash of Readest_0.12.12_x64-setup.exe?
Is it safe to install Readest_0.12.12_x64-setup.exe?
How up to date is this analysis of Readest_0.12.12_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.