Is NeoProgrammer.exe safe?
No engine detected a threat across 74 scanners, and the file has extensive historical prevalence without offensive behavior or corroborating malware intelligence.
All 74 antivirus engines were free of detections, including 17 tier-1 products, despite the file having about five years of exposure and 2,100 submissions. One sandbox observed direct-IP traffic, but no offensive techniques or malicious runtime verdict; the contacted endpoints were not fully reputation-checked.
36fed4eea63e808f9c…7b76931b87e717Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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 74 antivirus engines were free of detections, including 17 tier-1 products, despite the file having about five years of exposure and 2,100 submissions. One sandbox observed direct-IP traffic, but no offensive techniques or malicious runtime verdict; the contacted endpoints were not fully reputation-checked.
The strongest evidence is the absence of detections across 74 engines, including 17 tier-1 products. The executable is also widely encountered and approximately five years old, making an undetected established threat less likely. One completed sandbox run recorded three ambient techniques but no offensive techniques, persistence, dropped hashes, or malicious sandbox verdict. A heuristic highlighted direct-IP traffic, although the endpoint-reputation check was unavailable and the signal lacks independent corroboration. The executable is unsigned, but that concern is outweighed by its prevalence, long history, broad engine agreement, and lack of supporting threat intelligence.
What We Detected
No detections were reported by any of the 74 antivirus engines. This includes 17 tier-1 products, while external intelligence returned no MalwareBazaar hit, CIRCL match, or YARAify rule.
Threat Behavior
One completed sandbox run recorded three ambient techniques and no offensive techniques, persistence indicators, written files, or dropped hashes. A heuristic noted direct connections to multiple IP addresses, but no complete host-reputation result is available because the endpoint cross-check was not saved.
What To Do Now
The file has substantial historical prevalence, with 1,570 sources and 2,100 submissions over about five years. Its missing digital signature warrants obtaining it from the expected official source and keeping endpoint protection enabled during use.
Where this verdict could be wrong2 caveats
- signing.signed=false and signing.signerStats.found=false, so publisher identity and historical signer trust cannot support the file.
- MalwareTips.Synth.DirectIpC2 fired after direct-IP contacts were observed; contactedHosts=null prevents a complete reputation assessment of those endpoints.
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/74 antivirus engines reported a detection.
- All 17 tier-1 engines reported no detection.
- The file has 1,570 unique sources and 2,100 submissions over about five years.
- The completed sandbox run produced no malicious verdict and no offensive techniques.
- No packing, high-entropy code, malicious child, or external-intelligence match was found.
- The executable is unsigned and has no established signer history.
- Direct-IP traffic triggered MalwareTips.Synth.DirectIpC2.
- contactedHosts=null, so observed endpoints lack a complete reputation cross-check.
Use a copy obtained from the expected official source and verify its hash if the publisher provides one. Keep antivirus and endpoint protection enabled, particularly because the executable is unsigned.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were 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
- 3MITRE ATT&CK techniques
- 15spawned processes
- 20network 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
NeoProgrammer.exe
36fed4eea63e808f9ceb3eaa91a003690946a179df90787d757b76931b87e717
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\36fed4eea63e808f9ceb3eaa91a003690946a179df90787d757b76931b87e717.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\wuapihost.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
23.216.147.76
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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
- 23.216.147.76
- 20.99.132.105
- 13.107.4.50
- 20.99.184.37
- 20.99.133.109
- a83f:8110:0:0:2000:0:0:0
- 192.229.211.108
- 104.86.182.8
- 20.99.186.246
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EBE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F0D.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FA8.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FB9.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FF8.tmp.txt
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 / 74engines flagged
- 1,570sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,570 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 2,100 times from 1,570 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: NeoProgrammer.exe — 36fed4eea63e808f9ceb3eaa91a003690946a179df90787d757b76931b87e717
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\36fed4eea63e808f9ceb3eaa91a003690946a179df90787d757b76931b87e717.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 23.216.147.76 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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 · 23.216.147.76 · 20.99.132.105
0 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
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
- NeoProgrammer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.0 MB
- Last analyzed
- Sep 20, 2026, 11:31 AM UTC
36fed4eea63e808f9ceb3eaa91a003690946a179df90787d757b76931b87e717Safety & 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
Run it only when it came from the developer's official site or another source you independently 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 NeoProgrammer.exe safe?
What is NeoProgrammer.exe?
How many antivirus engines detected NeoProgrammer.exe?
What is the SHA-256 hash of NeoProgrammer.exe?
Is it safe to run NeoProgrammer.exe?
How up to date is this analysis of NeoProgrammer.exe?
Community
Member reviews and reports for this exact file hash.