Is Tsonic_win.exe safe?
Two low-trust engines flag an unsigned 2007-era EXE that shows no tier-1 detections or malicious sandbox outcome.
Only low-trust engines (APEX, Trapmine) flagged the file; 17 tier-1 engines remained silent. The sample is common_old with nearly a thousand submitters and no sandbox or child-file malice signals.
63162d4e6bef407dee…347ce4389c5b18Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Only low-trust engines (APEX, Trapmine) flagged the file; 17 tier-1 engines remained silent. The sample is common_old with nearly a thousand submitters and no sandbox or child-file malice signals.
The detection pattern matches the classic low-trust-only false-positive shape: two low_trust engines, zero tier-1 detections, and no family consensus. The file is unsigned, yet its 17-year prevalence and absence of malicious sandbox or dropped-child evidence outweigh the two low-trust labels. Offensive MITRE techniques were observed, but the sandbox returned no malicious verdict, and contacted-no complete contacted-host reputation result was available.
What We Detected
Two low-trust engines (APEX, Trapmine) reported malicious or suspicious-low-ml-score labels; 68 engines, including all 17 tier-1 engines, returned clean. The file is unsigned and contains no code-signing certificate.
Threat Behavior
Runtime analysis recorded MITRE techniques T1055 (process injection) and T1562.001 (impair defenses), yet the sandbox produced no malicious verdict. Ten dropped children were inspected and none flagged malicious. One host-reputation check returned no known-malicious or suspicious hosts.
What To Do Now
Keep endpoint protection enabled. The file can be executed in a controlled environment if further validation is required, but current evidence does not indicate active malice.
Where this verdict could be wrong1 caveat
- behaviour.offensiveTechniques include T1055 (process injection) and T1562.001 (impair defenses) — sandbox evidence is limited to one run and no malicious verdict recorded.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero tier-1 malicious detections
- Long-established prevalence (common_old)
- No malicious dropped children or sandbox verdict
- Unsigned executable
- Process-injection and defense-evasion techniques observed in sandbox
The file can be considered safe for normal use; continue running up-to-date endpoint protection.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 21MITRE ATT&CK techniques
- 14spawned processes
- 21network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Tsonic_win.exe
63162d4e6bef407dee30c2dc5840539ad013459caae2019f46347ce4389c5b18
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\Tsonic_win.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\GamePanel.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
d3d8caps.dat
C:\WINDOWS\system32\d3d8caps.dat
04Isolated runtime analysis - Written fileObserved
AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
13.107.4.52
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.132.105
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 13.107.4.52
- 20.99.132.105
- 20.80.129.13
- 23.216.147.64
- a83f:8110:4400:0:5000:0:0:0
- 20.99.133.109
- 23.216.147.76
- a83f:8110:4300:6400:5200:6f00:6d00:4d00
- 20.99.184.37
- 192.229.211.108
- http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl
- C:\WINDOWS\system32\d3d8caps.dat
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_85fcf44ecc2175a7f2c0caf9eb701db7dfba7986_de003304_1dfeab98
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_85fcf44ecc2175a7f2c0caf9eb701db7dfba7986_de003304_1dfeab98\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC61.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER309.tmp.WERInternalMetadata.xml
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4040.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4061.tmp.csv
- DirectSound DllMain mutex (0x000005D0)
- DDrawWindowListMutex
- __DDrawExclMode__
- __DDrawCheckExclMode__
- DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- d448168bd01c79abcd96…37b110Never scannednever seen before
- d8ba418ea26648bbca75…0c881cNever scannednever seen before
- b69aad0b774ef8dedd8f…bd6bccNever scannednever seen before
- e08d714d971602fbe26e…a2aa3bNever scannednever seen before
- 315f3fc5b3db399c8bf5…593c3aNever scannednever seen before
- 4c92dc634b27d0c985cb…66a967Never scannednever seen before
- 0f476078bb8a87ca4ec9…3bb1beNever scannednever seen before
- 209ed4de4eeff06de884…3a8f18Never scannednever seen before
- ef9e8d36c6ac75cbadc0…b6bd53Never scannednever seen before
- e8b8b3c1bf3e00bf11ae…ed73cbNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 2 / 74engines flagged
- 977sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash has a long, established submission history across 977 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
2 of 74 antivirus engines flagged the file, including APEX and Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: Tsonic_win.exe — 63162d4e6bef407dee30c2dc5840539ad013459caae2019f46347ce4389c5b18
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\Tsonic_win.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\GamePanel.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: d3d8caps.dat — C:\WINDOWS\system32\d3d8caps.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b — C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_program.exe_691143e83a29637bc129d4ab22fab9affbb31a_de003304_1f9ed75b
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.4.52 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.132.105 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\dllhost.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence13.107.4.52 · 20.99.132.105 · 20.80.129.13
2 of 74 engines flagged this file
View all 74 engine results
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Tsonic_win.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.9 MB
- Last analyzed
- Aug 8, 2026, 7:30 AM UTC
63162d4e6bef407dee30c2dc5840539ad013459caae2019f46347ce4389c5b18Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Tsonic_win.exe safe?
What is Tsonic_win.exe?
How many antivirus engines detected Tsonic_win.exe?
What is the SHA-256 hash of Tsonic_win.exe?
Is it safe to run Tsonic_win.exe?
How up to date is this analysis of Tsonic_win.exe?
Community
Member reviews and reports for this exact file hash.