Is 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2 safe?
No engine detected malware, runtime analysis found no offensive activity, and the long-established file contacted only fully checked, non-malicious hosts.
None of 75 antivirus engines flagged this file, including all 17 tier-1 engines. One completed sandbox run found no offensive techniques or malicious assessment, while all three observed network hosts received complete reputation coverage without malicious or suspicious results.
a4a085f27ae4bf50e6…a0ca77d54d358bRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
None of 75 antivirus engines flagged this file, including all 17 tier-1 engines. One completed sandbox run found no offensive techniques or malicious assessment, while all three observed network hosts received complete reputation coverage without malicious or suspicious results.
The strongest evidence is complete agreement across 75 engines, with no malicious or suspicious detections and all 17 tier-1 engines silent. One completed runtime observation produced no malicious sandbox assessment, offensive techniques, dropped hashes, or persistence indicators. All three observed domains were covered by the host-reputation check, with no malicious or suspicious matches. The file is also established rather than newly encountered, with 441 sources and 577 submissions over 1,122 days. Long-sleep and debugger-detection tags are weak counter-signals without independent corroboration, and contaminated sandbox text was excluded from consideration.
What We Detected
None of 75 antivirus engines reported a malicious or suspicious result. All 17 tier-1 engines, including BitDefender, ESET-NOD32, Kaspersky, Microsoft, and Avast, reported no detection. The file has also circulated for 1,122 days across 441 sources and 577 submissions.
Threat Behavior
One completed sandbox run found no offensive techniques, malicious assessment, persistence indicators, or dropped file hashes. The five recorded techniques were ambient system or application activity. All three observed domains were covered by the host-reputation check, and none matched malicious or suspicious records. Sandbox text marked as potentially instruction-like was ignored and did not influence the assessment.
What To Do Now
No malware-specific remediation is indicated by the available evidence. Keep endpoint protection enabled and obtain the file from a trusted source if its origin or purpose remains uncertain.
Where this verdict could be wrong2 caveats
- file.tags includes long-sleeps and detect-debug-environment, but no offensive technique, malicious sandbox assessment, engine detection, or persistence indicator corroborates those tags.
- adversarialInputFlags.sandboxTextInjectionSuspected=true indicates contaminated runtime text; that text was ignored, although the flag itself is not malware evidence.
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 malicious or suspicious detections.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false and behaviour.offensiveCount=0.
- contactedHosts.inspected=3 covered every observed domain with no malicious or suspicious matches.
- 441 unique sources and 577 submissions indicate long-established prevalence.
- file.tags includes long-sleeps and detect-debug-environment.
- adversarialInputFlags.sandboxTextInjectionSuspected=true, so contaminated runtime text was excluded.
No special cleanup is warranted from this evidence. Keep security protection enabled and verify the file's source before use if it arrived unexpectedly.
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
Complete3 contacted hosts were cross-checked.
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
- 5MITRE ATT&CK techniques
- 2spawned processes
- 3network contacts
- 12filesystem & 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.
- g-bing-com.ax-0001.ax-msedge.net
- g.bing.com
- www.bing.com
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.data
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.data\OpenWithList
- HKEY_CURRENT_USER_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\LangID
- HKEY_CURRENT_USER_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe.FriendlyAppName
- HKEY_CURRENT_USER_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe.ApplicationCompany
- HKEY_CURRENT_USER_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\Mozilla Firefox\firefox.exe.FriendlyAppName
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_16.db!dfMaintainer
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_32.db!dfMaintainer
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
- 441sources 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 hash has a long, established submission history across 441 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 577 times from 441 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2 — a4a085f27ae4bf50e65701a0c5e16d57c22af15d0dd446f551a0ca77d54d358b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\dense_text_classifier_v1_weights.data"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\OpenWith.exe C:\Windows\system32\OpenWith.exe -Embedding
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Explorer — C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: g-bing-com.ax-0001.ax-msedge.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: g.bing.com — 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
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2
- Format
- Text
- Code signing
- Not applicable to this file type
- Size
- 830.1 KB
- Last analyzed
- Oct 7, 2026, 5:23 AM UTC
a4a085f27ae4bf50e65701a0c5e16d57c22af15d0dd446f551a0ca77d54d358bSafety & 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
Open it only when its sender or download source is one 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 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2 safe?
What is 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2?
How many antivirus engines detected 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2?
What is the SHA-256 hash of 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2?
Is it safe to open 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2?
How up to date is this analysis of 8fbc1f3b5aa6c11d7fa90a8f2a580d026ec90055 2?
Community
Member reviews and reports for this exact file hash.