Is QA 06.04 Supplier Audit Report V5.xls safe?
No antivirus engine flagged this newly submitted Excel file.
All 74 engines returned clean results on a first-seen spreadsheet. No sandbox or external-intel data contradicts that finding.
73db31c0f309b3fb3c…f23446fb7b4373Recommended 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 74 engines returned clean results on a first-seen spreadsheet. No sandbox or external-intel data contradicts that finding.
The file is a 228 kB MS Excel spreadsheet submitted for the first time today. Every engine tier remained silent, including 17 tier-1 products. No code-signing, sandbox, or external-intel signals exist for this file type, and no heuristics fired. While the lack of runtime data leaves behaviour unverified, the complete absence of malicious detections across a broad engine set supports a safe classification.
What We Detected
74 engines scanned the file; none returned a malicious or suspicious result. The spreadsheet carries no digital signature and no sandbox trace is available.
Threat Behavior
No malicious indicators were observed in static analysis. No YARA rules, CIRCL entries, or MalwareBazaar records match the sample.
What To Do Now
Keep endpoint protection enabled. Open the file only if it originates from a trusted sender and macro execution is disabled.
Where this verdict could be wrong1 caveat
- Zero detections could reflect low coverage for .xls files rather than proven safety; absence of sandbox data leaves runtime behaviour unverified.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero malicious detections across 74 engines
- No external intelligence hits
The file can be considered safe for normal use, but treat any unexpected macro prompts with caution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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 / 74engines 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 74 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 74 engines flagged this file
View all 74 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
- QA 06.04 Supplier Audit Report V5.xls
- Format
- MS Excel Spreadsheet
- Code signing
- Not applicable to this file type
- Size
- 223.0 KB
- Last analyzed
- Jul 29, 2026, 6:38 PM UTC
73db31c0f309b3fb3cb495b20c70e0355b25ee33d1521e1e5af23446fb7b4373Safety & 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 QA 06.04 Supplier Audit Report V5.xls safe?
What is QA 06.04 Supplier Audit Report V5.xls?
How many antivirus engines detected QA 06.04 Supplier Audit Report V5.xls?
What is the SHA-256 hash of QA 06.04 Supplier Audit Report V5.xls?
Is it safe to open QA 06.04 Supplier Audit Report V5.xls?
How up to date is this analysis of QA 06.04 Supplier Audit Report V5.xls?
Community
Member reviews and reports for this exact file hash.