Is OmniControl Setup safe?
No antivirus engine detected malware, but the unsigned, newly observed installer produced process-injection and LSASS-access indicators that warrant caution pending publisher verification.
All 75 antivirus engines avoided flagging the file, and the completed sandbox did not issue a malicious result. However, this unsigned and newly observed installer generated process-injection and possible LSASS-access indicators, so it should not be run on a production system until its source and publisher are independently verified.
9131fdf209c8c6f630…46ce594dd83e56Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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 avoided flagging the file, and the completed sandbox did not issue a malicious result. However, this unsigned and newly observed installer generated process-injection and possible LSASS-access indicators, so it should not be run on a production system until its source and publisher are independently verified.
The strongest reassuring evidence is that 0 of 75 engines flagged the sample, including all 17 reporting tier-1 engines. One completed sandbox did not issue a malicious result, the observed host had no reputation-cache hit, and none of the 10 inspected children was identified as malware. Against that, runtime evidence mapped activity to T1055, T1134, and T1485, while a separate heuristic reported access involving LSASS. Those behaviours are unusually invasive for an installer, although they lack corroboration from engine detections or the sandbox verdict. Because the file is unsigned and was observed only once, there is insufficient publisher history to resolve these conflicting signals confidently.
What We Detected
No antivirus engine flagged the executable: 0 of 75 detections, with all 17 reporting tier-1 engines returning undetected results. The executable is unsigned and has only one recorded submission, so its publisher identity and distribution history cannot be established.
Threat Behavior
A completed sandbox run mapped activity to process injection (T1055), access-token manipulation (T1134), and file or directory destruction (T1485). A synthesized heuristic also reported process activity involving LSASS, which can resemble credential-access tooling. These indicators are concerning, but the sandbox itself did not issue a malicious result, no inspected child was identified as malware, and the fully covered observed host produced no malicious or suspicious reputation-cache hit.
What To Do Now
Do not test this installer on a production or sensitive computer. Verify its SHA-256 against the developer's official download channel and obtain a publisher-authenticated build if available; otherwise, keep endpoint protection enabled and use an isolated environment for further examination.
Where this verdict could be wrong4 caveats
- The antivirus results are uniformly undetected, including Avast, BitDefender, ESET-NOD32, Kaspersky, and 13 other reporting tier-1 engines.
- The completed sandbox assigned a clean result, and behaviour.hasMaliciousSandboxVerdict=false.
- contactedHosts.inspected=1 covered the one distinct observed host represented by the Microsoft domain and IP, with no malicious or suspicious cache hit.
- The T1055 and LSASS indicators come from synthesized behavioural mappings and are not corroborated by engine detections, malicious children, or a malicious sandbox verdict.
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 of 75 antivirus engines detected malware
- All 17 reporting tier-1 engines returned undetected
- Completed sandbox did not issue a malicious verdict
- No inspected child was identified as malicious
- Observed host was fully checked with no malicious or suspicious cache hit
- Unsigned Win32 executable with no authenticated publisher
- Only 1 submitter and 1 recorded submission
- Runtime mapping to T1055 process injection
- Heuristic evidence involving LSASS access
- Additional offensive mappings T1134 and T1485
- All 10 dropped-child verdicts remain unknown
Verify the SHA-256 with the software developer's official release channel before execution. If verification is unavailable, avoid installing it on a production system and keep endpoint protection enabled during isolated testing.
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 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 28MITRE ATT&CK techniques
- 11spawned processes
- 2network contacts
- 23filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
OmniControl Setup
9131fdf209c8c6f6303e5e1fceb967b38c996bcc5912e21bce46ce594dd83e56
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\OmniControl_2.9.13_x64-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nslDB1E.tmp
C:\Users\<USER>\AppData\Local\Temp\nslDB1E.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
atm.teams.mira.tm.svc.cloud.microsoft
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- atm.teams.mira.tm.svc.cloud.microsoft
- 162.159.36.2
- HKEY_CURRENT_USER\Software\Classes\omnicontrol\(Default)
- HKEY_CURRENT_USER\Software\Classes\omnicontrol\DefaultIcon\(Default)
- HKEY_CURRENT_USER\Software\Classes\omnicontrol\shell\open\command\(Default)
- HKEY_CURRENT_USER\SOFTWARE\OmniControl\OmniControl\(Default)
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\OmniControl\MainBinaryName
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\OmniControl\DisplayName
- C:\Users\<USER>\AppData\Local\Temp\nslDB1E.tmp
- C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsaDE3C.tmp
- C:\Users\<USER>\AppData\Local\Temp\nslE051.tmp
- C:\Users\user\AppData\Local\Temp\nsf86E9.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 0e83b004a42de15a0a23…c2f033Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 95290b2a204cf8a5c1e3…cc8df1Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 337bc20042b3ed9b3da0…ca7a31Never scannednever seen before
- 9e450e22e2b09ebba0ce…54013aNever scannednever seen before
- 8970badbdd299e9b7896…8ffa27Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 6a348f2587969164918f…9b8c29Never scannednever seen before
- e40b42b18e567f965ad5…7e78f3Never 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.
- 2rule hits recorded
- 0 / 75engines flagged
- 1sources 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 hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: OmniControl Setup — 9131fdf209c8c6f6303e5e1fceb967b38c996bcc5912e21bce46ce594dd83e56
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\OmniControl_2.9.13_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nslDB1E.tmp — C:\Users\<USER>\AppData\Local\Temp\nslDB1E.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nslDB6D.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: atm.teams.mira.tm.svc.cloud.microsoft — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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\Explorer.EXESandbox 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
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- OmniControl Setup
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 43.3 MB
- Last analyzed
- Oct 5, 2026, 2:23 AM UTC
9131fdf209c8c6f6303e5e1fceb967b38c996bcc5912e21bce46ce594dd83e56Safety & 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 open 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 original trusted source and verify its exact hash when possible.
- 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 OmniControl Setup safe, or is it malware?
What is OmniControl Setup?
How many antivirus engines detected OmniControl Setup?
I already downloaded and opened OmniControl Setup — what should I do?
How do I remove OmniControl Setup?
What is the SHA-256 hash of OmniControl Setup?
How up to date is this analysis of OmniControl Setup?
Community
Member reviews and reports for this exact file hash.