Is 012958FB-D66D-46EE-942D-F607A2FA59D0.png safe?
No antivirus engine detected a threat in this PNG, although the exact hash is newly observed and lacks completed runtime analysis.
All 75 antivirus engines returned no malicious or suspicious finding, including 17 tier-1 engines. The sample is a PNG image, and no threat family, malicious child, or corroborating intelligence hit was identified; however, it is newly observed and has no completed runtime data.
93f7b5a8e796c7a9ea…180bf2501e5112Recommended next actions
Before viewing
View it only when its sender or download source is one you trust.
If you already viewed 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 returned no malicious or suspicious finding, including 17 tier-1 engines. The sample is a PNG image, and no threat family, malicious child, or corroborating intelligence hit was identified; however, it is newly observed and has no completed runtime data.
The strongest evidence is complete detection silence: 0 of 75 engines flagged the file, including all 17 tier-1 participants. The object is identified as a PNG image, and code signing is not meaningful for this format. Neither the MalwareBazaar lookup nor the CIRCL lookup produced a hit, while the YARAify check timed out and therefore provides no conclusion. Five previous PNG-only matches received clean outcomes, though file-type similarity is weak evidence and does not establish that their contents are related. No sandbox execution or complete contacted-host reputation check is available, so the conclusion rests primarily on static scanning.
What We Detected
None of the 75 antivirus engines reported a malicious or suspicious result for this PNG. All 17 tier-1 engines were silent, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. MalwareBazaar and CIRCL also returned no matching record.
Threat Behavior
No completed sandbox observation is available, so no claims can be made about runtime behavior. There was also no saved contacted-host reputation check. The file is newly observed, and the YARAify lookup timed out, leaving limited uncertainty beyond the otherwise consistent static results.
What To Do Now
The image can be handled normally while keeping endpoint protection enabled. If it arrived unexpectedly or from an untrusted sender, open it only with an updated image viewer and rescan if its contents or file type appear unusual.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new: this exact hash has only 1 submission and was first observed today.
- behaviour=null and contactedHosts=null, so runtime activity and contacted-host reputation were not evaluated.
- externalIntel.availability.yaraify=error, leaving a researcher-rule coverage gap.
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 result.
- All 17 tier-1 engines reported no detection.
- file.mimeType=image/png matches file.fileType=PNG.
- externalIntel.malwareBazaar.hit=false and externalIntel.circl.hit=false.
- 5/5 file-type-similar records have prior safe decisions.
- The exact hash has only 1 recorded submission and was first observed today.
- No completed runtime observation is available.
- No complete contacted-host reputation result is available.
- The YARAify lookup timed out.
Normal use is reasonable based on the static evidence, but keep endpoint protection enabled. Treat unexpected images cautiously and rescan if the source or displayed content seems inconsistent.
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
PartialIndependent reference checks were attempted but are incomplete.
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
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved 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.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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
- 012958FB-D66D-46EE-942D-F607A2FA59D0.png
- Format
- PNG
- Code signing
- Not applicable to this file type
- Size
- 1.8 MB
- Last analyzed
- Sep 28, 2026, 3:11 PM UTC
93f7b5a8e796c7a9ea10e558879375fe83a079528e3169b129180bf2501e5112Safety & 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
View it only when its sender or download source is one you 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 012958FB-D66D-46EE-942D-F607A2FA59D0.png safe?
What is 012958FB-D66D-46EE-942D-F607A2FA59D0.png?
How many antivirus engines detected 012958FB-D66D-46EE-942D-F607A2FA59D0.png?
What is the SHA-256 hash of 012958FB-D66D-46EE-942D-F607A2FA59D0.png?
Is it safe to view 012958FB-D66D-46EE-942D-F607A2FA59D0.png?
How up to date is this analysis of 012958FB-D66D-46EE-942D-F607A2FA59D0.png?
Community
Member reviews and reports for this exact file hash.