Is Near.zip safe?
Zero detections across 75 engines, no sandbox malice, and no external-intel hits on a medium-prevalence archive.
All 75 engines returned clean. Sandbox execution produced no malicious verdict and no malicious children were dropped. The two triggered heuristics explicitly note they do not prove malicious intent.
68e9dc9b559d8a1728…54140da19b5c14Recommended 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 75 engines returned clean. Sandbox execution produced no malicious verdict and no malicious children were dropped. The two triggered heuristics explicitly note they do not prove malicious intent.
With zero malicious detections from any engine tier and no corroborating external-intel or sandbox malice, the file shows no malware indicators. The two MITRE mappings (T1055, T1562.001) are flagged by heuristics that themselves state the evidence is inconclusive. Medium prevalence and two-day age are consistent with a newly circulating but clean portable archive.
What We Detected
75 engines scanned the ZIP; none flagged it malicious or suspicious. Sandbox execution recorded process-injection and direct-IP heuristics, but the accompanying evidence text states these do not prove malicious intent. Ten dropped children were inspected and none were malicious.
Threat Behavior
No C2 domains, no complete contacted-host reputation result was available contacts, and no persistence or registry changes were observed. The contacted IP 162.159.36.2 has no prior malicious classification in our cache.
What To Do Now
The archive can be treated as clean. Continue to keep endpoint protection enabled and only open archives from trusted sources.
Where this verdict could be wrong1 caveat
- triggeredHeuristics fired MalwareTips.Synth.ProcessInjection (high) and MalwareTips.Synth.DirectIpC2 (low) — these heuristics map to T1055 and direct-IP traffic but the evidence text states they do not prove malicious intent.
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 engine detections across all tiers
- No malicious sandbox verdict
- No malicious dropped children
- No external-intel hits
Open the archive only if you trust the source; keep antivirus enabled.
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
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 9MITRE ATT&CK techniques
- 5spawned processes
- 1network contacts
- 23filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Near.zip
68e9dc9b559d8a17286cc5ef88f5bcfe22a7bca16ed27f882954140da19b5c14
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Near/Default/openh264-2.2.0-win64.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 5716 -s 556
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
eab7e16d-e918-4662-81e5-4d42b356c066
C:\ProgramData\Microsoft\Windows\WER\Temp\eab7e16d-e918-4662-81e5-4d42b356c066
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\eab7e16d-e918-4662-81e5-4d42b356c066
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\c908bf5f-340e-45c0-a612-8a73f12d366d
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE7B.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD293.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3EC.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE7B.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD293.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess5716
- Global\ab79c3a4-0f6f-4995-87b6-04a2d827384b
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 5e49edf72e0444e1fb58…3493edNever scannednever seen before
- 27ce32f1148a6f43fc4e…584ad1Never scannednever seen before
- 9b392bf05cff1199cc44…23d2d0Never scannednever seen before
- 94e6b1ec9b852e463816…808b57Never scannednever seen before
- aae3ed80132889311446…9b4c6dNever scannednever seen before
- 12464bdc78dfcffe8571…4d5038Never scannednever seen before
- a218875fd4036095a7fd…6c3f79Never scannednever seen before
- 102f2689d1328efc8c1f…72ca64Never scannednever seen before
- 12be98f0dc5ded63ff78…04c574Never scannednever seen before
- e089f65899c81b232326…accc3bNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 15sources 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 16 times from 15 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Near.zip — 68e9dc9b559d8a17286cc5ef88f5bcfe22a7bca16ed27f882954140da19b5c14
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Near/Default/openh264-2.2.0-win64.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 5716 -s 556
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: eab7e16d-e918-4662-81e5-4d42b356c066 — C:\ProgramData\Microsoft\Windows\WER\Temp\eab7e16d-e918-4662-81e5-4d42b356c066
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Near/Default/openh264-2.2.0-win64.dll",#1The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Near.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 8.2 MB
- Last analyzed
- Aug 25, 2026, 2:05 AM UTC
68e9dc9b559d8a17286cc5ef88f5bcfe22a7bca16ed27f882954140da19b5c14Safety & 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 Near.zip safe?
What is Near.zip?
How many antivirus engines detected Near.zip?
What is the SHA-256 hash of Near.zip?
Is it safe to open or extract Near.zip?
How up to date is this analysis of Near.zip?
Community
Member reviews and reports for this exact file hash.