Is NETworkManager_2026.7.7.0_Setup.msi safe?
No antivirus engine detected this signed installer, but one sandbox recorded process-injection and protection-impairment indicators that warrant cautious source verification.
All 75 antivirus engines were silent, including 17 high-trust engines, and the installer carries a verified SignPath Foundation signature. However, one sandbox associated its activity with process injection, protection impairment, and possible LSASS targeting, while the signer's history is too small to provide strong reassurance.
26b4ced4ed8ff48ed1…8bbdb47d171824Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
All 75 antivirus engines were silent, including 17 high-trust engines, and the installer carries a verified SignPath Foundation signature. However, one sandbox associated its activity with process injection, protection impairment, and possible LSASS targeting, while the signer's history is too small to provide strong reassurance.
The installer received no detection from any of 75 antivirus engines, which substantially lowers the likelihood of established malware. Its signature verifies as SignPath Foundation, but only two historical samples are available for that signer, so publisher history is not yet conclusive. One completed sandbox did not issue a malicious verdict, although its telemetry mapped activity to T1055 and T1562.001 and prompted an LSASS-related heuristic. Those mappings are concerning but do not establish the exact injection or credential-access action from the saved process evidence alone. A signer-matched prior file also received a cautious assessment, so source verification remains appropriate despite the otherwise favorable scan results.
What We Detected
No antivirus engine flagged the installer: 0 of 75 reported a malicious or suspicious result, including all 17 tier-1 engines. The MSI has a verified signature from SignPath Foundation, no brand mismatch was detected, and external research sources supplied no matching malware or YARA intelligence.
Threat Behavior
One completed sandbox did not produce a malicious verdict, but the recorded telemetry was mapped to process injection (T1055) and impairment of defenses (T1562.001). A separate heuristic associated the process list with possible LSASS targeting. The available evidence shows svchost.exe and lsass.exe processes but does not prove a specific injection method or credential-memory read, so these findings may reflect overbroad behavioral attribution. Three hosts were checked without a reputation hit, although that inspection count does not fully cover every distinct recorded domain, IP address, and URL.
What To Do Now
Confirm the SHA-256 hash and download source against the project's official release channel before installation. Keep endpoint protection enabled and, if the source cannot be authenticated, test the MSI in an isolated environment or obtain a fresh official copy.
Where this verdict could be wrong4 caveats
- The antivirus result is strongly favorable: 0/75 engines detected the file, including no detections from 17 tier-1 engines.
- The sole completed sandbox labeled its run clean and behaviour.hasMaliciousSandboxVerdict=false.
- The process-injection and credential-dumper heuristics rely on broad process evidence involving svchost.exe and lsass.exe; the saved data does not establish an exact injection or memory-reading operation.
- The file has a verified 'SignPath Foundation' signature and no detected brand mismatch.
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 detection.
- All 17 tier-1 engines reported no detection.
- The SignPath Foundation signature is verified.
- behaviour.hasMaliciousSandboxVerdict=false.
- No malicious child, brand mismatch, MalwareBazaar match, or YARAify rule was recorded.
- Sandbox telemetry mapped activity to T1055 process injection.
- Sandbox telemetry mapped activity to T1562.001 impairment of defenses.
- MalwareTips.Synth.CredentialDumper associated process activity with lsass.exe.
- SignPath Foundation has only 2 historical samples in signing.signerStats.
- One signer-matched similar hash previously received reasonCode ai:signed_but_unusual_behaviour.
Install only after verifying the hash and origin through the software project's official release channel. Keep antivirus and endpoint protection enabled during installation and use isolation if provenance remains uncertain.
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
Partial3 of 5 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 7MITRE ATT&CK techniques
- 9spawned processes
- 9network contacts
- 12filesystem & 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: Used removable-media replication behaviour that can spread files between devices.
High concern: Attempted to impair or bypass security controls.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 5 servers during sandbox analysis.
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
NETworkManager_2026.7.7.0_Setup.msi
26b4ced4ed8ff48ed10b484a7c25580f6fce545c18643461428bbdb47d171824
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\NETworkManager_2026.7.7.0_Setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis - Written fileObserved
Cab1A0C.tmp
C:\Users\<USER>\AppData\Local\Temp\Cab1A0C.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
ocsp.globalsign.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
cdn-default.globalsigncdn.com
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.
- ocsp.globalsign.com
- cdn-default.globalsigncdn.com
- prod.globalsign.map.fastly.net
- 8.8.8.8
- 151.101.194.133
- http://ocsp.globalsign.com/codesigningrootr45/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVFZP5vqhCrtRN5SWf40Rn6NM1IAQUHwC%2FRoAK%2FHg5t6W0Q9lWULvOljsCEHe9DgOhtwj4VKsGchDZBEc%3D
- http://ocsp.globalsign.com/gsgccr45codesignca2020/ME0wSzBJMEcwRTAJBgUrDgMCGgUABBTLuA3ygnKW%2F7xuSx%2F09F%2BhHVuEUQQU2rONwCSQo2t30wygWd0hZ2R2C3gCDBiDgM%2Fh%2BD6nB8ZbKA%3D%3D
- http://ocsp.globalsign.com/codesigningrootr45/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVFZP5vqhCrtRN5SWf40Rn6NM1IAQUHwC/RoAK/Hg5t6W0Q9lWULvOljsCEHe9DgOhtwj4VKsGchDZBEc=
- http://ocsp.globalsign.com/gsgccr45codesignca2020/ME0wSzBJMEcwRTAJBgUrDgMCGgUABBTLuA3ygnKW/7xuSx/09F+hHVuEUQQU2rONwCSQo2t30wygWd0hZ2R2C3gCDBiDgM/h+D6nB8ZbKA==
- 4EFC31460C619ECAE59C1BCE2C008036D94C84B8\Blob
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\4EFC31460C619ECAE59C1BCE2C008036D94C84B8\Blob
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Temp\Cab1A0C.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tar1A0D.tmp
- C:\MSI4b906.tmp
- C:\ProgramData
- C:\Users\<USER>\AppData\Local\Temp\Cab1A0C.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tar1A0D.tmp
- C:\MSI4b906.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:7052:304:WilStaging_02
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 34sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from SignPath Foundation.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: NETworkManager_2026.7.7.0_Setup.msi — 26b4ced4ed8ff48ed10b484a7c25580f6fce545c18643461428bbdb47d171824
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\NETworkManager_2026.7.7.0_Setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Cab1A0C.tmp — C:\Users\<USER>\AppData\Local\Temp\Cab1A0C.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: ocsp.globalsign.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: cdn-default.globalsigncdn.com — 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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
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.exe
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- NETworkManager_2026.7.7.0_Setup.msi
- Format
- Windows Installer
- Code signing
- Signature valid: SignPath Foundation
- Size
- 27.8 MB
- Last analyzed
- Oct 6, 2026, 7:37 AM UTC
26b4ced4ed8ff48ed10b484a7c25580f6fce545c18643461428bbdb47d171824Safety & 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 install 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. Download a fresh installer 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 NETworkManager_2026.7.7.0_Setup.msi safe, or is it malware?
What is NETworkManager_2026.7.7.0_Setup.msi?
How many antivirus engines detected NETworkManager_2026.7.7.0_Setup.msi?
What should I do if I already installed NETworkManager_2026.7.7.0_Setup.msi?
How do I remove NETworkManager_2026.7.7.0_Setup.msi?
Is NETworkManager_2026.7.7.0_Setup.msi digitally signed?
What is the SHA-256 hash of NETworkManager_2026.7.7.0_Setup.msi?
How up to date is this analysis of NETworkManager_2026.7.7.0_Setup.msi?
Community
Member reviews and reports for this exact file hash.