Is 4c6abbca-56b0-4a94-baf7-5004bb3769c4 safe?
No engine among 76 detected the three-year-old ZIP, and independent intelligence produced no malware matches, although its contents were not dynamically observed.
All 76 antivirus engines avoided malicious or suspicious classifications, including 18 tier-1 products, and external intelligence returned no matches. The archive has limited prevalence, and no sandbox execution or complete network-reputation check is available, so caution remains appropriate when extracting unknown contents.
5d795616eba8addee6…36a8a9d2d53928Recommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted 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 76 antivirus engines avoided malicious or suspicious classifications, including 18 tier-1 products, and external intelligence returned no matches. The archive has limited prevalence, and no sandbox execution or complete network-reputation check is available, so caution remains appropriate when extracting unknown contents.
The strongest evidence is broad antivirus agreement: 0 of 76 engines flagged the archive, including no detections from 18 tier-1 products. Research intelligence also found no MalwareBazaar, CIRCL, or YARAify match. The sample has been known for roughly three years, reducing concern that it is merely too new for signatures, though only four submissions are recorded. Code-signing evidence is not applicable to a ZIP archive. Because no completed sandbox observation exists, this assessment cannot establish what enclosed files would do after extraction. No complete contacted-host reputation result is available either.
What We Detected
No malicious or suspicious detection was reported by any of 76 antivirus engines. All 18 tier-1 engines that contributed results, including BitDefender, Kaspersky, ESET-NOD32, Fortinet, and McAfee, reported no detection. MalwareBazaar, CIRCL, and YARAify also returned no match.
Threat Behavior
No completed sandbox run is available, so the archive's contents were not observed executing. There is also no complete host-reputation result because contacted-host checking was not saved or completed. The sample has existed for about three years but was submitted only four times, indicating limited circulation.
What To Do Now
Keep endpoint protection enabled and scan extracted files before opening them. If the archive arrived unexpectedly or from an untrusted sender, verify its source and inspect the enclosed filenames before execution.
Where this verdict could be wrong3 caveats
- prevalence.uniqueSources=4 indicates limited distribution despite the sample's age.
- behaviour=null means the archive and any enclosed files were not observed executing.
- contactedHosts=null means no complete host-reputation result is available.
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/76 engines reported malicious or suspicious results
- 18 tier-1 engines reported no detection
- No MalwareBazaar, CIRCL, or YARAify match
- Known for approximately 1,097 days
- No fired heuristics or detected brand mismatch
- No completed sandbox observation of the archive contents
- No complete contacted-host reputation result
- Limited prevalence: 4 submissions from 4 sources
- Opaque UUID-style filename provides little provenance
Keep endpoint protection enabled, scan every extracted item, and open the archive only if its source and expected contents are trustworthy.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 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 / 76engines flagged
- 4sources 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 76 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 4 times from 4 sources.
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 76 engines flagged this file
View all 76 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- 4c6abbca-56b0-4a94-baf7-5004bb3769c4
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 35.5 MB
- Last analyzed
- Sep 30, 2026, 4:22 AM UTC
5d795616eba8addee6d24343bf42d395061d9646e9864c41b536a8a9d2d53928Safety & 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 or extract it only when its sender or download source has been independently verified.
- 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 4c6abbca-56b0-4a94-baf7-5004bb3769c4 safe?
What is 4c6abbca-56b0-4a94-baf7-5004bb3769c4?
How many antivirus engines detected 4c6abbca-56b0-4a94-baf7-5004bb3769c4?
What is the SHA-256 hash of 4c6abbca-56b0-4a94-baf7-5004bb3769c4?
Is it safe to open or extract 4c6abbca-56b0-4a94-baf7-5004bb3769c4?
How up to date is this analysis of 4c6abbca-56b0-4a94-baf7-5004bb3769c4?
Community
Member reviews and reports for this exact file hash.