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
What this file did when executed
This file was detonated in 5 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
26MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1027· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1069
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1112
- T1115
- T1125
- T1129· Loads modules
- T1134
- T1222
- T1485
- T1486· File encryption
- T1497· Sandbox evasion
- T1529
- T1547.009· Auto-start
- T1553
- T1553.002
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
Clatterbox_0.1.1_x64-setup.exe"C:\Users\<USER>\Desktop\Clatterbox_0.1.1_x64-setup.exe"Clatterbox_0.1.1_x64-setup.exe"C:\Users\user\Desktop\Clatterbox_0.1.1_x64-setup.exe"
Files
21Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\nsh4300.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsh4301.tmp\System.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsh4301.tmp\modern-wizard.bmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsh4301.tmp\nsDialogs.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsh4301.tmp\nsis_tauri_utils.dll - Written
C:\Users\<USER>\AppData\Local\Clatterbox\clatterbox.exe
Show all 21 entries for files
- Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\CREDITS.md - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-01.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-02.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-03.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-04.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-05.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-06.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-07.wav - Written
C:\Users\<USER>\AppData\Local\Clatterbox\packs\classic\down-08.wav - Deleted
C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update - Deleted
C:\Users\<USER>\AppData\Local\Temp\nsp851F.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\nsk8550.tmp - Deleted
C:\Users\user\AppData\Local\Temp\nsj5459.tmp - Deleted
C:\Users\user\AppData\Local\Temp\nsn3805.tmp
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\SOFTWARE\zordhalo\Clatterbox\(Default) - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\MainBinaryName - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\DisplayName - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\DisplayIcon - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\DisplayVersion - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\Publisher
Show all 15 entries for registry and auto-start
- Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\InstallLocation - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\UninstallString - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\NoModify - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\NoRepair - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Clatterbox\EstimatedSize - Set
HKEY_CURRENT_USER\SOFTWARE\zordhalo\Clatterbox\Installer Language - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\UFH\SHC\0 - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search\InstalledWin32AppsRevision - Set
HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
cversions.3.mGlobal\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
8The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 8 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM process
lsass.exeC:\Windows\system32\lsass.exe
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- f00e2b09066cf37426b2…96d350Not checkedno saved verdict
- e212b1c2dcf5c4296628…018b85Not checkedno saved verdict
- 5ba143b5db4a87d32d6e…ad4709Not checkedno saved verdict
- 35119784ec1917747a1f…d31265Not checkedno saved verdict
- 79de7a9cc035ca420460…7ba86cNot checkedno saved verdict
- 4455b731037c01a6a665…02b80eNot checkedno saved verdict
- 39df76e16d6daa76619f…634678Not checkedno saved verdict
- b66c58738b2d02b210df…8fcb3cNot checkedno saved verdict
- 813ef394935bd69d9169…cb9c64Not checkedno saved verdict
- 0be1fe122b8da67c0ce9…4a8d92Not checkedno saved verdict
Chapter 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.
Antivirus consensus
2 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-235 engines0flagged
- Low-trust17 engines2flagged
View all 75 engine results
- APEXMalicious: Malicious
- CylanceMalicious: Unsafe
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 2 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Chapter 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.