Is word_Lab1[3][44].docx safe?
No engine among 75 detected a threat in this DOCX, and no static heuristic or external intelligence source supplied contrary evidence.
All 75 antivirus engines were free of detections, including 17 high-trust engines, and no static heuristic fired. The document is newly observed and lacks sandbox coverage, so normal caution remains appropriate when opening an unexpected attachment.
91839cc5d8df9b023f…640e73c0d45760Recommended 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.
All 75 antivirus engines were free of detections, including 17 high-trust engines, and no static heuristic fired. The document is newly observed and lacks sandbox coverage, so normal caution remains appropriate when opening an unexpected attachment.
The document received no malicious or suspicious detections from 75 antivirus engines, with all 17 participating high-trust engines reporting no detection. No heuristic fired, and the available external intelligence checks produced no matching threat indicators. Signing is not applicable to this DOCX format, so the absence of a signature carries no negative weight. Five prior documents of the same file type received safe decisions, although file-type-only similarity is weak supporting evidence. The exact hash is newly observed, and no completed runtime or contacted-host reputation results are available.
What We Detected
No malicious or suspicious result appeared among 75 antivirus engines. Seventeen high-trust engines, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Fortinet, reported no detection. No static heuristic fired, and the available external intelligence checks returned no matching indicators.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be characterized. Likewise, no complete contacted-host reputation result is available. The file is an Office Open XML document, and code signing is not applicable to this format.
What To Do Now
The scan evidence does not identify a threat. Because the exact document is newly observed, open it only if its source and purpose are expected, keep Office and endpoint protection enabled, and avoid enabling unexpected external content or following unsolicited links.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new with 1 submitter and 1 submission, so the exact hash has almost no established history.
- behaviour=null and contactedHosts=null, leaving runtime activity and contacted-host reputation unverified.
- The 5/5 similar safe samples are matchKind=filetype only and therefore are not strong hash-level similarity.
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 findings.
- engines.tier1ReportedClean=17 and engines.tier1Malicious=0.
- triggeredHeuristics contains no fired rules.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- 5/5 similarHashes entries have verdict='safe', though all are file-type-only matches.
- prevalence.classification=rare_new: the exact hash has only 1 submission from 1 source.
- behaviour=null: no completed runtime observation is available.
- contactedHosts=null: no complete host-reputation cross-check is available.
The available scan evidence supports opening the document if it came from an expected source. Keep endpoint protection and Office security features enabled, and do not trust unexpected prompts or links.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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 behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 1sources 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
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved 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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- word_Lab1[3][44].docx
- Format
- Office Open XML Document
- Code signing
- Not applicable to this file type
- Size
- 23.2 KB
- Last analyzed
- Oct 6, 2026, 4:31 AM UTC
91839cc5d8df9b023f6df70bb4670330932b716c57b21b0378640e73c0d45760Safety & 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 word_Lab1[3][44].docx safe?
What is word_Lab1[3][44].docx?
How many antivirus engines detected word_Lab1[3][44].docx?
What is the SHA-256 hash of word_Lab1[3][44].docx?
Is it safe to open word_Lab1[3][44].docx?
How up to date is this analysis of word_Lab1[3][44].docx?
Community
Member reviews and reports for this exact file hash.