Is NepTunnel 2.2.exe safe?
Five of 74 engines flagged this unsigned proxy utility, while runtime injection and LSASS-related indicators plus multiple YARA matches warrant substantial caution.
The executable has no verified publisher and drew five detections among 74 engines, including a ProxyAgent riskware label, though no tier-1 engine flagged it. Runtime evidence mapped to process injection and LSASS-related activity, and multiple research rules matched, so it should not be trusted without source verification.
41b01a63bcb94d3466…597740bc9f2402Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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 executable has no verified publisher and drew five detections among 74 engines, including a ProxyAgent riskware label, though no tier-1 engine flagged it. Runtime evidence mapped to process injection and LSASS-related activity, and multiple research rules matched, so it should not be trusted without source verification.
Five of 74 engines raised alerts, but the set contains no tier-1 detection or agreed malware family. The executable is unsigned and lacks publisher history, which weakens confidence in its origin. One sandbox recorded indicators mapped to T1055 and T1486, plus LSASS-related process activity, although it did not issue an explicit malicious runtime judgment. Eight research rules matched, but the disclosed set includes generic PyInstaller and debugger-detection rules that do not establish a family by themselves. The two contacted IP addresses were not fully reputation-checked, and all ten extracted children remain unclassified, leaving important uncertainty.
What We Detected
Five of 74 antivirus engines flagged the executable. Malwarebytes identified RiskWare.ProxyAgent.Python, Gridinsoft used a generic bot-risk label, and three lower-trust engines supplied broad malware or unsafe labels. No tier-1 engine detected it, and there is no tier-1 family consensus.
Threat Behavior
A completed sandbox run recorded activity mapped to T1055 and T1486, while a separate heuristic associated process activity with LSASS. The file also contacted two IP addresses directly, but no complete host-reputation result is available for those contacts. Eight research rules matched; disclosed matches include debugger checks and PyInstaller-identification rules, which add concern but are not independently conclusive. Ten extracted files were inspected without a known malicious child, although every child remains unclassified.
What To Do Now
Do not run the file on a production or personal system unless its source and expected proxy functionality can be independently verified. Keep endpoint protection enabled, obtain the program from an official release channel, and compare its SHA-256 value with a publisher-provided checksum before considering isolated testing.
Where this verdict could be wrong4 caveats
- tier1Malicious=0, while 14 tier-1 engines including BitDefender, ESET-NOD32, Kaspersky, and Fortinet reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false, although the 10 inspected children all remain unclassified.
- The disclosed YARA rules include Detect_PyInstaller and PyInstaller, which identify packaging technology and are not independently proof of malware.
- The five similar-hash results are imphash-only matches without signer co-matching, so shared build tooling may account for the similarity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- tier1Malicious=0 and 14 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false
- prevalence.uniqueSources=265 across 324 submissions
- Unsigned Win32 executable with no established signer history
- 5/74 antivirus detections, including RiskWare.ProxyAgent.Python
- Runtime evidence mapped to T1055 process injection
- LSASS-related activity raised a credential-dumper heuristic
- externalIntel.yaraify.ruleCount=8
- Two direct IP contacts without a complete host-reputation check
Quarantine the executable pending verification from an official publisher or release channel, and avoid entering credentials or granting elevated privileges. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete5 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete8 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
- 16MITRE ATT&CK techniques
- 9spawned processes
- 2network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
NepTunnel 2.2.exe
41b01a63bcb94d3466ada5e9df375ab92cd777377270aebd09597740bc9f2402
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\NepTunnel 2.2.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_avif.cp314-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imaging.cp314-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.18.14.72
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
199.232.192.193
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 104.18.14.72
- 199.232.192.193
- C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_avif.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imaging.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imagingcms.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imagingft.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imagingmath.cp314-win_amd64.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never 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.
- 8rule hits recorded
- 5 / 74engines flagged
- 265sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
5 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 8 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: NepTunnel 2.2.exe — 41b01a63bcb94d3466ada5e9df375ab92cd777377270aebd09597740bc9f2402
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\NepTunnel 2.2.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _avif.cp314-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_avif.cp314-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp314-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI55242\PIL\_imaging.cp314-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.18.14.72 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 199.232.192.193 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
One or more independent reference databases matched 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.
- DebuggerCheck__API
- DebuggerException__SetConsoleCtrl
- Detect_PyInstaller
- golang_bin_JCorn_CSC846
- PyInstaller
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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence104.18.14.72 · 199.232.192.193
5 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- NepTunnel 2.2.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 19.1 MB
- Last analyzed
- Sep 21, 2026, 1:15 AM UTC
41b01a63bcb94d3466ada5e9df375ab92cd777377270aebd09597740bc9f2402Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is NepTunnel 2.2.exe safe, or is it malware?
What is NepTunnel 2.2.exe?
How many antivirus engines detected NepTunnel 2.2.exe?
What should I do if I already ran NepTunnel 2.2.exe?
How do I remove NepTunnel 2.2.exe?
What kind of malware is NepTunnel 2.2.exe?
What is the SHA-256 hash of NepTunnel 2.2.exe?
How up to date is this analysis of NepTunnel 2.2.exe?
Community
Member reviews and reports for this exact file hash.