Is NS-RPC-windows-installer.exe safe?Safe
This unsigned installer for the open-source NS-RPC project shows no high-trust malicious signals, with only low-trust engines flagging it, consistent with common false-positive patterns for community-developed software.
- 2 of 74 antivirus engines flagged the file, including Cylance and Trapmine.
- The hash has been submitted 65 times from 60 sources.
ca22633bae88e927bb…65e277eac9Before opening
Confirm that the file came from the source you expected before opening it.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Coverage & freshness
A completed check means the source returned a result. It does not, by itself, guarantee that the file is safe.
Antivirus
Complete2 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial11 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.
Attack story
A bounded view of the runtime evidence saved with this scan. Connectors mean “also observed,” not a proven causal chain.
- File
NS-RPC-windows-installer.exe
ca22633bae88…77eac9
Observed - Process
Observed process
%SAMPLEPATH%\NS-RPC-windows-installer.exe
Observed - Process
Observed process
C:\Windows\System32\wuapihost.exe
Observed - Written file
Program Files (x86)
C:\Program Files (x86)
Observed - Written file
Microsoft
C:\Program Files (x86)\Microsoft
Observed - Contacted host
20.69.140.28
Contact observed during runtime.
Observed - Contacted host
192.229.211.108
Contact observed during runtime.
Observed
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 74 antivirus engines flagged the file, including Cylance and Trapmine.
Antivirus analysisView chapterVerdict inputObserved - 02
The hash has been submitted 65 times from 60 sources.
Saved report factsView chapterDerived
Intelligence
The complete saved assessment, kept intact and grounded in the scan evidence.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Our analysis indicates this file is a legitimate installer for the NS-RPC project. The detections are limited to low-trust engines and lack corroboration from high-trust antivirus vendors or malicious behavioral indicators.
The file is an unsigned installer for a known open-source project, which explains the lack of a digital signature. While two low-trust engines flagged the file, no tier-1 engines identified it as malicious, and the behavioral analysis showed no evidence of actual compromise or malicious activity. The direct IP connections flagged by our heuristics are typical for certain installer frameworks. Given the age of the file and the lack of corroborating malicious signals, we consider this a false-positive scenario.
What We Detected
The file 'NS-RPC-windows-installer.exe' was analyzed across 74 antivirus engines. Only 2 low-trust engines provided generic 'Unsafe' or 'suspicious' labels, while all 17 tier-1 engines remained silent. The file is unsigned, which is common for community-driven open-source projects.
Threat Behavior
The file exhibited installer-like behavior, including creating directories and mutexes associated with update processes. While a heuristic rule flagged direct IP connections, these are consistent with standard installer network activity and did not involve any known malicious infrastructure.
What To Do Now
This file appears to be a legitimate community-developed tool. If you obtained this file from the official project repository, it is likely safe to use. Ensure you always download software from trusted, official sources to maintain system integrity.
Where this verdict could be wrong2 caveats
- The 'MalwareTips.Synth.DirectIpC2' heuristic flagged direct IP connections, which could be interpreted as suspicious behavior in a more restrictive environment.
- The lack of a digital signature prevents verification of the publisher, leaving the file's integrity reliant on the source repository.
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/17 tier-1 engines malicious
- no malicious sandbox verdict
- no malicious contacted hosts
- medium prevalence (65 submissions)
- unsigned executable
- direct IP connections
The file is likely safe for use. Ensure it was downloaded from the official project repository.
Behavior
Plain-English impact first, then the observed runtime evidence.
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.
- 20.69.140.28
- 192.229.211.108
- 20.99.184.37
- 23.216.147.76
- 20.99.185.48
- 20.99.186.246
- 23.62.210.8
- 23.196.193.245
- a83f:8110:0:0:b00:b00:2800:1800
- 23.216.147.12
- C:\Program Files (x86)
- C:\Program Files (x86)\Microsoft
- C:\Program Files (x86)\Microsoft\EdgeUpdate
- C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.143.57
- C:\Program Files (x86)\Microsoft\EdgeUpdate\Download
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER14BB.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1577.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER15B6.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3013.tmp.WERInternalMetadata.xml
- \Sessions\1\BaseNamedObjects\_Microsoft_EdgeUpdate_logging_mutex_C:ProgramDataMicrosoftEdgeUpdateLogMicrosoftEdgeUpdate.log
- \Sessions\1\BaseNamedObjects\Global\EdgeUpdate{F340B839-380B-4AA9-BA6F-B83F23E2DD05}
- \Sessions\1\BaseNamedObjects\Global\EdgeUpdate{DDDDEAEB-04CC-4BAA-9C63-CCA5FE38F688}
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
- \Sessions\1\BaseNamedObjects\Global\EdgeUpdate{921D73A1-67B6-4E73-81EA-8A162D92D990}
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- d78c5bc9972b06ce256c…df7cb1Never scannednever seen before
- 784d1df23f232b5e4d40…f36d0fNever scannednever seen before
- bd9699e3da3de9521455…20f668Never scannednever seen before
- 8f53160721cbb335c5b4…5b7e06Never scannednever seen before
- c1346ac1f12d9b2d8ed4…6d4368Never scannednever seen before
- dcd5baa50714c59de372…5a4bbfNever scannednever seen before
- 8e110a20684c92438b3e…b5009aNever scannednever seen before
- 7ebc4ce80143ef89cea8…e11c3aNever scannednever seen before
- 91d3fc490565ded7621f…1145f5Never scannednever seen before
- 7d3f4e7a5ecfa260582b…a80b9cNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
Sample contacted 11 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence20.69.140.28 · 192.229.211.108 · 20.99.184.37
2 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
- NS-RPC-windows-installer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 5.2 MB
- Last analyzed
- Jul 23, 2026, 9:22 PM UTC
ca22633bae88e927bba2e96c43920f4cafb93c77a000e4922d0f0365e277eac9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file looks safe based on everything we checked.
This file is safe to use.
Good habit: only download files from the official website or an app store.
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
- NS-RPC-windows-installer.exe appears safe. 2 of 74 antivirus engines flagged it; the 2 low-confidence detections were treated as likely false positives. As a habit, only run files you downloaded from the official source, since attackers sometimes distribute trojanised copies of legitimate software under the same name.
- NS-RPC-windows-installer.exe is a Windows executable program, about 5.2 MB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- 2 of 74 antivirus engines flagged NS-RPC-windows-installer.exe, 2 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- The SHA-256 hash of NS-RPC-windows-installer.exe is ca22633bae88e927bba2e96c43920f4cafb93c77a000e4922d0f0365e277eac9, and its MD5 is 1b014f5ff25719146e1287a45af16ab8. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- Based on the recorded evidence, NS-RPC-windows-installer.exe has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
- This report reflects the scan run on July 23, 2026. Because a file's hash never changes, the identity of NS-RPC-windows-installer.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.