Is bwUnin-6.2.3.66.exe safe?
Single low-trust engine flag on an unsigned 17-year-old file with no sandbox or tier-1 corroboration.
Only one low-trust engine flagged the sample; all tier-1 engines returned clean. No sandbox malice, no dropped children, and no external-intel hits support a clean verdict.
bdc3508469923899ce…be388aa9da13c2Recommended 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 one low-trust engine flagged the sample; all tier-1 engines returned clean. No sandbox malice, no dropped children, and no external-intel hits support a clean verdict.
The single detection originates from MaxSecure, a low-trust engine, while 16 tier-1 engines and 75 total engines reported undetected. The file is unsigned, yet its 6360-day history and medium prevalence show no tier-1 consensus or malicious sandbox verdict. The triggered heuristic notes direct-IP traffic but explicitly cautions against C2 conclusions without host-reputation data, which is unavailable. Similar-hash RAG and external intelligence sources are silent.
What We Detected
One low-trust engine (MaxSecure) produced the label Trojan.Malware.300983.susgen; 74 other engines, including all 17 tier-1 engines, returned clean. The file is an unsigned 90 kB Win32 EXE first seen in 2009.
Threat Behavior
Sandbox execution recorded one offensive MITRE technique (T1547.001) and benign ambient activity. No malicious sandbox verdict, no dropped children, and no domain contacts were observed. The single contacted IP lacks host-reputation coverage.
What To Do Now
Keep endpoint protection enabled. The evidence indicates a benign or at worst obsolete utility; no action beyond normal caution is required.
- 16 tier-1 engines clean
- medium prevalence over 17 years
- no sandbox malice or dropped children
The file can be considered safe for normal use; retain existing security software and avoid disabling protections.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was 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
- 12MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 4filesystem & 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
bwUnin-6.2.3.66.exe
bdc3508469923899ced08dc7c7038c604dac5a4e3537a2fe6abe388aa9da13c2
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\software.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Microsoft Compatibility Appraiser
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis
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.
- 162.159.36.2
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\<USER>\Desktop\.bak
- BackWebSettings
- \Sessions\1\BaseNamedObjects\BackWebSettings
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
- 1 / 75engines flagged
- 9sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 18 times from 9 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: bwUnin-6.2.3.66.exe — bdc3508469923899ced08dc7c7038c604dac5a4e3537a2fe6abe388aa9da13c2
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Microsoft Compatibility Appraiser — C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — 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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
1 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
- bwUnin-6.2.3.66.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 88.0 KB
- Last analyzed
- Aug 19, 2026, 3:43 AM UTC
bdc3508469923899ced08dc7c7038c604dac5a4e3537a2fe6abe388aa9da13c2Safety & 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 bwUnin-6.2.3.66.exe safe?
What is bwUnin-6.2.3.66.exe?
How many antivirus engines detected bwUnin-6.2.3.66.exe?
What is the SHA-256 hash of bwUnin-6.2.3.66.exe?
Is it safe to run bwUnin-6.2.3.66.exe?
How up to date is this analysis of bwUnin-6.2.3.66.exe?
Community
Member reviews and reports for this exact file hash.