Is tbox-img.exe safe?
All 75 antivirus engines were silent, the Tencent signature verified, and completed runtime analysis found no offensive behavior or malicious verdict.
No antivirus engine detected this executable, including all 17 tier-1 engines. Its Tencent signature is valid, and one completed sandbox run found no offensive-only behavior, malicious child, persistence indicator, or malicious runtime verdict.
f3885e479c78123008…772e9fcc5203aaRecommended 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.
No antivirus engine detected this executable, including all 17 tier-1 engines. Its Tencent signature is valid, and one completed sandbox run found no offensive-only behavior, malicious child, persistence indicator, or malicious runtime verdict.
The strongest evidence is complete agreement across 75 antivirus engines, with no malicious or suspicious result. The executable carries a verified signature from Tencent Technology (Shenzhen) Company Limited, and no conflicting brand identity was detected. One completed sandbox run recorded common techniques but no offensive-only technique or malicious verdict. The observed domain was www.microsoft.com and its reputation check found no concern, although the listed IP addresses lack documented reputation coverage. Independent malware databases and researcher rules supplied no corroborating hit, while the PE structure showed neither packing nor high-entropy code.
What We Detected
None of the 75 antivirus engines flagged the executable, including all 17 tier-1 engines. The file has a verified digital signature from Tencent Technology (Shenzhen) Company Limited, and the metadata shows no brand conflict. Independent intelligence checks returned no MalwareBazaar sample match or YARAify rule match.
Threat Behavior
One completed sandbox run recorded ten techniques commonly seen in installers and ordinary applications, but no offensive-only technique, persistence indicator, dropped payload, or malicious runtime verdict. The only recorded domain, www.microsoft.com, was inspected without a malicious or suspicious result. The six listed IP addresses do not have documented reputation coverage in this evidence, so the network assessment is not fully comprehensive.
What To Do Now
The evidence supports normal use when the file came from Tencent or another expected official distribution channel. Keep endpoint protection enabled and verify the source and signature before execution if the file arrived unexpectedly.
Where this verdict could be wrong3 caveats
- signing.signerStats.found=false, so no historical sample record is available to establish this signer's reliability.
- Runtime metadata includes T1027 and T1497.001, but behaviour.offensiveCount=0 and the completed sandbox did not issue a malicious verdict.
- contactedHosts.inspected=1 documents coverage for www.microsoft.com but not the six IP addresses listed in behaviour.contactedIps, so host-reputation coverage is incomplete.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- The signature for 'Tencent Technology (Shenzhen) Company Limited' verified successfully.
- One sandbox produced no malicious verdict and behaviour.offensiveCount=0.
- peAnalysis.likelyPacked=false and externalIntel.yaraify.ruleCount=0.
- No historical signer statistics are available for 'Tencent Technology (Shenzhen) Company Limited'.
- Runtime metadata includes obfuscation and virtual-environment-evasion-related technique identifiers T1027 and T1497.001.
- Reputation coverage is incomplete for the six IP addresses in behaviour.contactedIps.
Use the file only if its Tencent origin and purpose are expected, and retain endpoint protection during installation or execution. Re-download it from the official source if its provenance is uncertain.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 7 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 10MITRE ATT&CK techniques
- 8spawned processes
- 7network contacts
- 10filesystem & mutex artifacts
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.
- www.microsoft.com
- 20.22.113.133
- 192.229.211.108
- 192.168.0.11
- 23.32.75.15
- 23.213.37.172
- 20.99.133.109
- \Device\ConDrv\\Connect
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER265F.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2660.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER272A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER272B.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER276B.tmp.txt
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 25sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from Tencent Technology (Shenzhen) Company Limited.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 26 times from 25 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: tbox-img.exe — f3885e479c78123008148850a18d72f4d99ab5226c3ccf207c772e9fcc5203aa
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\tbox-img.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 09
Contacted host: 20.22.113.133 — 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- tbox-img.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Tencent Technology (Shenzhen) Company Limited
- Size
- 2.4 MB
- Last analyzed
- Sep 24, 2026, 6:10 PM UTC
f3885e479c78123008148850a18d72f4d99ab5226c3ccf207c772e9fcc5203aaSafety & 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 tbox-img.exe safe?
What is tbox-img.exe?
How many antivirus engines detected tbox-img.exe?
Is tbox-img.exe digitally signed?
What is the SHA-256 hash of tbox-img.exe?
Is it safe to run tbox-img.exe?
How up to date is this analysis of tbox-img.exe?
Community
Member reviews and reports for this exact file hash.