Is tvpwin32.exe safe?
Two of 75 engines detected downloader behavior, while direct-IP contacts and absent signing warrant caution despite no tier-1 or research-source corroboration.
Only 2 of 75 engines flagged this executable, and none of the tier-1 engines detected it. However, it is unsigned and one sandbox run recorded five direct-IP contacts whose reputations were not checked, so it should not be run without further verification.
9dc5fb0993379d5c4d…45f66f25fb2348Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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 2 of 75 engines flagged this executable, and none of the tier-1 engines detected it. However, it is unsigned and one sandbox run recorded five direct-IP contacts whose reputations were not checked, so it should not be run without further verification.
Gridinsoft and Jiangmin flagged the sample as a downloader, with Jiangmin assigning the Banload name, but no tier-1 engine supported either label. One sandbox run observed five external IP contacts and triggered the direct-IP heuristic, though it produced no malicious sandbox conclusion or offensive-only technique. Because host-reputation coverage is unavailable, those connections cannot be characterized as benign or malicious. The executable is unsigned, which removes a useful publisher-authentication signal. Its long history, broad tier-1 non-detection, unpacked structure, and lack of external-intelligence hits make a false positive plausible, leaving materially mixed evidence.
What We Detected
Two of 75 antivirus engines flagged the executable. Gridinsoft used a generic downloader label, while Jiangmin named Banload; none of the tier-1 engines corroborated those detections.
Threat Behavior
One completed sandbox run recorded connections to five external IP addresses and triggered the MalwareTips.Synth.DirectIpC2 heuristic. No offensive-only techniques, persistence indicators, dropped files, or malicious sandbox conclusion were recorded. The contacted-host reputation check was not completed or saved, so the observed addresses cannot be described as clean or malicious.
What To Do Now
Do not execute the file on a production system unless its source and expected purpose can be independently verified. Keep endpoint protection enabled, obtain a fresh copy from the official publisher if possible, and use an isolated analysis environment if further inspection is necessary.
Where this verdict could be wrong4 caveats
- Sixteen tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet.
- behaviour.hasMaliciousSandboxVerdict=false and behaviour.offensiveCount=0, although one sandbox run cannot exclude dormant or environment-dependent activity.
- The file has been known since 2018 and has 83 submitting sources, which weighs against a newly distributed threat.
- No external research source corroborated the Banload label, and peAnalysis found neither packing nor high-entropy code.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine detection or family consensus
- Sixteen tier-1 engines reported no detection
- No malicious sandbox conclusion or offensive-only technique
- No CIRCL, MalwareBazaar, or YARAify corroboration
- No packing or high-entropy code detected
- Unsigned Win32 executable with no established signer history
- Two antivirus detections identify downloader behavior
- One engine associates the file with Banload
- Five direct-IP contacts were observed during sandbox execution
- No complete reputation check is available for the contacted IP addresses
Quarantine the file pending source verification and avoid running it on a normal workstation. Keep security protection enabled and replace it with a copy obtained directly from a verified publisher channel.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 5MITRE ATT&CK techniques
- 3spawned processes
- 5network contacts
- 19filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
tvpwin32.exe
9dc5fb0993379d5c4d02f0e20ee2f9fc223190e1bd9b3921c745f66f25fb2348
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\tvpwin32.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.184.37
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
192.229.211.108
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 20.99.184.37
- 192.229.211.108
- 23.209.116.25
- 23.216.147.64
- 20.99.186.246
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER27A7.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER27A8.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2892.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C3.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2882.tmp.csv
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 2 / 75engines flagged
- 83sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 75 antivirus engines flagged the file, including Gridinsoft and Jiangmin.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 109 times from 83 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: tvpwin32.exe — 9dc5fb0993379d5c4d02f0e20ee2f9fc223190e1bd9b3921c745f66f25fb2348
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — %SAMPLEPATH%\tvpwin32.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 192.229.211.108 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence20.99.184.37 · 192.229.211.108 · 23.209.116.25
2 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
- tvpwin32.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.2 MB
- Last analyzed
- Sep 19, 2026, 9:29 AM UTC
9dc5fb0993379d5c4d02f0e20ee2f9fc223190e1bd9b3921c745f66f25fb2348Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is tvpwin32.exe safe, or is it malware?
What is tvpwin32.exe?
How many antivirus engines detected tvpwin32.exe?
What should I do if I already ran tvpwin32.exe?
How do I remove tvpwin32.exe?
What is the SHA-256 hash of tvpwin32.exe?
How up to date is this analysis of tvpwin32.exe?
Community
Member reviews and reports for this exact file hash.