File scan report
Verdict Safe
Is Near.
Zero detections across 75 engines, no sandbox malice, and no external-intel hits on a medium-prevalence archive.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Open the archive only if you trust the source; keep antivirus enabled.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website you got it from.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 67 flagged
- Flagged 0
- No detection 67
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 67 antivirus engines that checked it returned clean. Sandbox execution produced no malicious verdict and no malicious files it created were dropped. The two triggered rules 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 are flagged by rules 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. Ten files it created were inspected and none were malicious.
Threat Behavior
No control-server 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 security software enabled and only open archives from trusted sources.
Where this verdict could be wrong1 caveat
- triggeredHeuristics fired one of our behaviour rules (high) and one of our behaviour rules (low) — these rules map to 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 files it created
- No external-intel hits
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 9sandbox rule tags
- 3spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
9MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1497· Sandbox evasion
- T1562.001· Disables security
- T1574· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Near/Default/openh264-2.2.0-win64.dll",#1unarchiver.exeC:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\Near.zip"7za.exeC:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\zqepem0s.axr" "C:\Users\user\Desktop\Near.zip"
Files
21Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\eab7e16d-e918-4662-81e5-4d42b356c066 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\c908bf5f-340e-45c0-a612-8a73f12d366d - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\1e1cba42-40f5-443d-a66a-bc0cefebdecc
Show all 21 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\0ffc82de-4595-4071-8b1f-99aa61af780c - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\289f9897-e5a1-40e7-a2e6-b91a1a47cb9a - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\8cc19d26-1fbd-4c14-b675-47d2ed71ea09 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE7B.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD293.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3EC.tmp.xml - Written
C:\Users\user\AppData\Local\Temp\unarchiver.log - Written
C:\Users\user\AppData\Local\Temp\zqepem0s.axr - Written
C:\Users\user\AppData\Local\Temp\zqepem0s.axr\Near - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE7B.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD293.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3EC.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE7B.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD293.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3EC.tmp.xml
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess5716Global\ab79c3a4-0f6f-4995-87b6-04a2d827384b
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 5716 -s 556 - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 5e49edf72e0444e1fb58…3493edNot checkedno saved verdict
- 27ce32f1148a6f43fc4e…584ad1Not checkedno saved verdict
- 9b392bf05cff1199cc44…23d2d0Not checkedno saved verdict
- 94e6b1ec9b852e463816…808b57Not checkedno saved verdict
- aae3ed80132889311446…9b4c6dNot checkedno saved verdict
- 12464bdc78dfcffe8571…4d5038Not checkedno saved verdict
- a218875fd4036095a7fd…6c3f79Not checkedno saved verdict
- 102f2689d1328efc8c1f…72ca64Not checkedno saved verdict
- 12be98f0dc5ded63ff78…04c574Not checkedno saved verdict
- e089f65899c81b232326…accc3bNot checkedno saved verdict
Chapter 04
Technical details
None of the 67 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Aug 25, 2026, 2:05 AM UTC
- SHA-256
68e9dc9b559d8a17286cc5ef88f5bcfe22a7bca16ed27f882954140da19b5c14- SHA-1
053b99b9f0812ee6b2bb2c84bfa14e01cb68aad6- MD5
a070bef681b1c04609729adb7f8b2141
About this file
Near.zip is a ZIP file of 8.6 MB.
- Type and size
- ZIP · 8.6 MB
- Signer
- Not applicable
- First seen
- Aug 22, 2026On VirusTotal.
- Submitted by
- 15 distinct sources
First scanned
Antivirus consensus
0 of 67 engines flagged this file
8 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-237 engines0flagged
- Low-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.