Is NBTExplorer-master.zip safe?
No antivirus engine detected the long-established archive, and neither runtime analysis nor researcher-curated intelligence produced a corroborated malware finding.
The archive received no detections from 75 antivirus engines, including 17 tier-1 engines, and has circulated broadly since 2018. One sandbox recorded a defense-evasion technique and direct-IP contact, but produced no malicious runtime verdict; the contacted IP was not reputation-checked completely.
097a92d5b7dc5a1798…50983d267dc459Recommended 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.
The archive received no detections from 75 antivirus engines, including 17 tier-1 engines, and has circulated broadly since 2018. One sandbox recorded a defense-evasion technique and direct-IP contact, but produced no malicious runtime verdict; the contacted IP was not reputation-checked completely.
All 75 antivirus engines were free of malicious or suspicious detections, including 17 tier-1 products. The archive is long-established and common, with 579 submissions from 552 sources since 2018. One completed sandbox run produced no malicious verdict, and none of the 10 inspected extracted children was identified as malicious. Researcher-curated intelligence supplied no YARA, known-malware, or malware-repository match. The T1562.001 observation and direct-IP connection are counter-signals, but they lack engine, sandbox-verdict, child, or external-intelligence corroboration. Because host-reputation coverage was not completed, the no complete contacted-host reputation result was available.
What We Detected
The archive was not flagged by any of 75 antivirus engines, including all 17 reporting tier-1 engines. It has also been observed since 2018, with 579 submissions from 552 distinct sources, indicating broad and long-running distribution.
Threat Behavior
One sandbox run recorded T1562.001 and a direct connection to 204.79.197.203, but it did not issue a malicious runtime verdict. Ten extracted children were inspected without a malicious identification, although their individual verdicts remain unknown. No complete host-reputation result is available because contactedHosts was not checked or saved.
What To Do Now
Keep endpoint protection enabled and obtain the archive from the project's official release channel where possible. If its origin is uncertain, inspect the extracted executable separately before running it.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques contains T1562.001, an impairment-of-defenses technique, but the sandbox supplied no malicious verdict.
- MalwareTips.Synth.DirectIpC2 fired after contact with 204.79.197.203; contactedHosts=null means no complete host-reputation result is available.
- droppedChildren.rollup reports 10 unknown children, so hasMaliciousChild=false does not establish that every extracted component is benign.
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 antivirus engines reported a malicious or suspicious detection.
- All 17 reporting tier-1 engines returned no detection.
- The file has 579 submissions from 552 sources dating to 2018.
- behaviour.hasMaliciousSandboxVerdict=false.
- No YARAify, CIRCL, or MalwareBazaar hit was present.
- Runtime evidence includes MITRE technique T1562.001.
- The sample contacted 204.79.197.203 directly without a recorded application domain.
- contactedHosts=null, so reputation coverage for the observed IP is incomplete.
- All 10 extracted-child verdicts are unknown.
Use a copy obtained from the project's official source and keep endpoint protection enabled. Scan any extracted executable separately before launch if the archive came from an unverified download.
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
Complete1 signature or behavior rule 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
- 5MITRE ATT&CK techniques
- 4spawned processes
- 1network contacts
- 15filesystem & 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
NBTExplorer-master.zip
097a92d5b7dc5a17980da115084d53e936114d9fcce14e714d50983d267dc459
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\NBTExplorer-master/References/Substrate.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\sample.zip
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
kel5ivyp.wdv
C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv
04Isolated runtime analysis - Written fileObserved
NBTExplorer-master
C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
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.
- 204.79.197.203
- C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv
- C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master
- C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master\.gitignore
- C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master\LICENSE.txt
- C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master\NBTExplorer
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- d90a760ede93af2a1f0b…63c9b7Never scannednever seen before
- 8915695a60dedc4841fe…5956dcNever scannednever seen before
- bcac6281b0bd1a25e81c…1aff6fNever scannednever seen before
- 78c185e4bcb5cbeb2d6b…8c0cfeNever scannednever seen before
- d8a0b6d70ee6879e3754…02b127Never scannednever seen before
- abdf113061cadcc1d9b5…3b52faNever scannednever seen before
- 5a4e3029aeee54be988d…ef70b3Never scannednever seen before
- 75c3cfbcf69c657987df…fd6607Never scannednever seen before
- d980b5947b622cc53b33…4b0fc5Never scannednever seen before
- c894e1b2b4e8b40d9485…1f34d4Never 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 552sources 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 552 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 579 times from 552 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: NBTExplorer-master.zip — 097a92d5b7dc5a17980da115084d53e936114d9fcce14e714d50983d267dc459
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\NBTExplorer-master/References/Substrate.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\sample.zip
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: kel5ivyp.wdv — C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: NBTExplorer-master — C:\Users\user\AppData\Local\Temp\kel5ivyp.wdv\NBTExplorer-master
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — 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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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.
Evidence204.79.197.203
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
- NBTExplorer-master.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 701.8 KB
- Last analyzed
- Sep 14, 2026, 9:40 PM UTC
097a92d5b7dc5a17980da115084d53e936114d9fcce14e714d50983d267dc459Safety & 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 NBTExplorer-master.zip safe?
What is NBTExplorer-master.zip?
How many antivirus engines detected NBTExplorer-master.zip?
What is the SHA-256 hash of NBTExplorer-master.zip?
Is it safe to open or extract NBTExplorer-master.zip?
How up to date is this analysis of NBTExplorer-master.zip?
Community
Member reviews and reports for this exact file hash.