Is support.ico safe?
No engine detected this long-established ICO file, and its broad prevalence plus absent threat-intelligence matches provide strong benign evidence.
None of 75 antivirus engines flagged this icon file, including 17 tier-1 engines. It has circulated widely since 2012, with 13,550 submissions from 3,707 sources, and no external threat-intelligence service matched it; however, no completed runtime or contacted-host assessment is available.
05fe749ef47d1ec862…57cb79cec5eb20Recommended 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 icon file, including 17 tier-1 engines. It has circulated widely since 2012, with 13,550 submissions from 3,707 sources, and no external threat-intelligence service matched it; however, no completed runtime or contacted-host assessment is available.
The scan produced zero malicious or suspicious detections among 75 engines, with all 17 tier-1 participants reporting no detection. The ICO file has been observed since 2012 and submitted 13,550 times by 3,707 distinct sources, which strongly reduces concern about an emerging threat. MalwareBazaar, YARAify, and CIRCL supplied no corroborating threat match. Code signing is not meaningful for an ICO file, so the absence of a signature does not count against it. No completed sandbox observation or comprehensive contacted-host reputation check is available, but the extensive static and prevalence evidence supports benign use.
What We Detected
None of 75 antivirus engines flagged the file as malicious or suspicious. All 17 tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. MalwareBazaar, YARAify, and CIRCL also returned no matching threat intelligence.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be characterized. Likewise, no comprehensive contacted-host reputation check was saved. The sample is an ICO icon file, and code signing is not applicable to this format.
What To Do Now
The file has substantial established prevalence: 13,550 submissions from 3,707 sources since 2012. It can be retained when it came from the expected application or website; keep endpoint protection enabled and rescan if its contents or source change.
Where this verdict could be wrong3 caveats
- behaviour=null, so the file was not supported by completed runtime observation.
- contactedHosts=null, so no complete host-reputation cross-check is available.
- file.tags includes 'via-tor', but this contextual tag is not corroborated by engine detections or threat-intelligence hits.
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 a malicious or suspicious detection.
- 17 tier-1 engines reported no detection.
- Observed since 2012 across 3,707 sources and 13,550 submissions.
- MalwareBazaar, YARAify, and CIRCL returned no threat match.
- No brand mismatch or malicious dropped-child evidence was present.
- No completed runtime observation is available.
- No comprehensive contacted-host reputation result is available.
- The contextual file.tags array includes 'via-tor', without independent threat corroboration.
Retain or use the icon when it came from the expected source. Keep endpoint protection enabled and rescan any replacement or modified copy.
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
- 3,707sources 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 3,707 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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
- support.ico
- Format
- ICO
- Code signing
- Not applicable to this file type
- Size
- 61.4 KB
- Last analyzed
- Sep 23, 2026, 4:48 AM UTC
05fe749ef47d1ec862d6c55be78e66d1011226bf1f78409acf57cb79cec5eb20Safety & 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 support.ico safe?
What is support.ico?
How many antivirus engines detected support.ico?
What is the SHA-256 hash of support.ico?
Is it safe to open support.ico?
How up to date is this analysis of support.ico?
Community
Member reviews and reports for this exact file hash.