File scan report
Verdict Safe
Is Clatterbox_
Only 2 of the 70 antivirus engines that checked it raised generic warnings, while higher-confidence engines stayed silent and the sandbox runs supplied no corroborating malicious…
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
2 of 70 flagged
- Flagged 2
- No detection 68
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen Today
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
The two generic detections appear more likely to be false positives than evidence of malware. Higher-confidence engines did not flag the installer, and the combined sandbox verdict was clean without named injection targets or sample network contacts. Because it is unsigned and rarely submitted, obtain it from the developer’s official release channel.
APEX and Cylance were the only 2 of the 70 antivirus engines that checked it to flag the installer, and neither supplied a real malware-family name. All 18 reporting higher-confidence engines returned no detection. The combined sandbox verdict was clean, with no named injection target, high-risk technique, persistence indicator, or sample network contact recorded. No malware-specific community rules, public sample-database listing, or malicious file it created corroborated the warnings. The file is nevertheless unsigned, first seen on Oct 27, 2026, and submitted by only one source, so its origin should be verified before execution. Similar files built with the same import table mostly received clean assessments, but those matches involve different publishers and add little weight.
What We Detected
APEX and Cylance flagged the installer with generic labels, accounting for 2 of the 70 antivirus engines that checked it. None of the 18 reporting higher-confidence engines detected it, and no engine identified a specific malware family.
Threat Behavior
The combined sandbox verdict was clean. The runs recorded ordinary installer activity, including writing application files and uninstall information, but no named injection target, high-risk technique, persistence indicator, or sample network contact.
What To Do Now
The generic detections are likely false positives, but the installer is unsigned and has almost no distribution history. Download it only from the developer’s official release channel, verify its SHA-256 where the developer publishes one, and keep security software enabled while installing.
Where this verdict could be wrong3 caveats
- The executable is unsigned and was submitted by only one source, so it lacks an established publisher or distribution history.
- Our static analysis was not available because the bytes were not uploaded, so the installer’s contents were not independently inspected.
- APEX and Cylance both raised generic warnings, although no higher-confidence engine or independent intelligence source 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.
- Only 2 of the 70 antivirus engines that checked it flagged the file, and all reporting higher-confidence engines remained silent.
- The combined sandbox verdict was clean and recorded no named injection target or sample network contact.
- No malware-specific community rules or public sample-database listing matched the hash.
- No inspected dropped file had a malicious or suspicious saved verdict.
- The antivirus analysis found no packing or unusually high-entropy code.
- The Windows executable is unsigned, so its publisher cannot be authenticated through code signing.
- It was first seen on Oct 27, 2026 and had been submitted by only one source.
- APEX and Cylance raised generic warnings.
- The installer’s contents were not independently examined by our static analysis.
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 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 26sandbox rule tags
- 2spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
Includes the sandbox verdicts, 26 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
2 of the 70 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.
Engines that flagged it 2
The saved verdict treats these detections as likely false positives.
- APEXMalicious
- CylanceUnsafe
File fingerprint
- Last analyzed
- Oct 27, 2026, 1:44 PM UTC
- SHA-256
1aec8f3c35bc0727006c98c3c380fd99860347aec5c646779a0f093b43da79c0- SHA-1
38b5a94f4b7c99fe4e8e2e247ec6dde2f4faed95- MD5
4b3d54621d9a98c56e0270ff5c361644
About this file
Clatterbox_0.1.1_x64-setup.exe says it is Clatterbox, 2.9 MB.
- Claims to be
- ClatterboxFrom the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 2.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 27, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.05 of 8
First scanned
Verdict history
- Not fully confirmed
- Safe
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 Clatterbox_0.1.1_x64-setup.exe safe?
What is Clatterbox_0.1.1_x64-setup.exe?
How many antivirus engines detected Clatterbox_0.1.1_x64-setup.exe?
What is the SHA-256 hash of Clatterbox_0.1.1_x64-setup.exe?
Is it safe to install Clatterbox_0.1.1_x64-setup.exe?
How up to date is this analysis of Clatterbox_0.1.1_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.