Is Pixillion.exe safe?
No antivirus engine detected malware, and the verified NCH Software signature plus broad prevalence outweigh generic YARA and sandbox technique mappings.
All 75 antivirus engines avoided a malware or suspicious detection, including 17 tier-1 engines, and the executable carries a verified NCH Software signature. Some sandbox mappings and three generic YARA matches are concerning, but the completed sandbox did not issue a malicious result and no inspected child was identified as malicious.
090808d2df9151a806…0e913bb0993239Recommended 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 75 antivirus engines avoided a malware or suspicious detection, including 17 tier-1 engines, and the executable carries a verified NCH Software signature. Some sandbox mappings and three generic YARA matches are concerning, but the completed sandbox did not issue a malicious result and no inspected child was identified as malicious.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with 17 tier-1 engines reporting clean. The executable is verified as signed by NCH Software and has been submitted 715 times by 593 sources, fitting established commercial software rather than a newly appearing payload. One completed sandbox mapped activity to credential-access and process-injection techniques, but its final result was clean and the observed RunOnce entry is compatible with installer completion. Three community YARA rules matched, although their names and descriptions indicate broad certificate, overlay, and anti-analysis patterns rather than a specific malware family. Ten inspected child files produced no malicious finding, while host-reputation coverage was incomplete because only six of the many observed network endpoints were inspected.
What We Detected
None of 75 antivirus engines flagged the executable, and all 17 reporting tier-1 engines avoided a malware detection. The file has a verified digital signature from NCH Software and is well established, with 715 submissions from 593 sources over 574 days.
Threat Behavior
One completed sandbox recorded a RunOnce installation entry and mapped activity to T1003 and T1055, including an LSASS-related indicator. These mappings deserve attention, but the sandbox itself returned a clean result, and the saved evidence does not establish a specific injection method or credential theft. YARAify matched Check_Wine, PE_Digital_Certificate, and Sus_Obf_Enc_Spoof_Hide_PE; these are broad structural or anti-analysis rules rather than family-specific detections, and one explicitly notes possible false positives. None of the 10 inspected child files was identified as malicious. Only six contacted hosts were reputation-checked despite additional observed IPs and a URL, so complete network reputation coverage is unavailable.
What To Do Now
Use the installer only if it came from NCH Software's official distribution channel and its signature still verifies before execution. Keep endpoint protection enabled, and rescan if the signature changes or unexpected credential-access alerts recur.
Where this verdict could be wrong4 caveats
- The sandbox mapped activity to T1003 and T1055, including an LSASS-related indicator, which is unusual for image-conversion software even though the completed sandbox verdict was clean.
- YARAify returned 3 rule matches, but two are generic structural or anti-analysis checks and Sus_Obf_Enc_Spoof_Hide_PE explicitly warns that it can produce false positives.
- signing.signerStats.found=false, so no historical publisher sample record is available to reinforce the verified NCH Software signature.
- contactedHosts.inspected=6 does not cover every distinct domain, IP, and URL observed during execution, so no complete host-reputation conclusion is available.
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 malware or suspicious content.
- 17 tier-1 engines reported clean.
- The signature verifies for NCH Software.
- The sample has 715 submissions from 593 sources.
- No malicious child was found among 10 inspected files.
- Runtime evidence mapped activity to T1003 credential access.
- Runtime evidence mapped activity to T1055 process injection.
- A RunOnce persistence entry named PixillionInstall was created.
- YARAify matched 3 broad community rules.
- No historical signer statistics are available for NCH Software in signing.signerStats.
- Contacted-host reputation coverage was incomplete.
Obtain the file from NCH Software's official channel and confirm the digital signature before use. Keep endpoint protection enabled and investigate if execution generates independent credential-access or process-injection alerts.
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
Partial6 of 26 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete6 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
- 37MITRE ATT&CK techniques
- 15spawned processes
- 27network contacts
- 40filesystem & mutex artifacts
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.
- secure.nch.com.au
- res.public.onecdn.static.microsoft
- www.microsoft.com
- www.nch.com.au
- www.bing.com
- time.windows.com
- 173.247.253.164
- 20.99.185.48
- 192.168.0.25
- 23.64.172.197
- 23.219.160.229
- 20.99.133.109
- 184.27.218.92
- 20.99.186.246
- 217.20.54.35
- a83f:8110:0:0:100:0:1800:0
- http://www.bing.com/favicon.ico
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\PixillionInstall
- HKEY_CURRENT_USER\SOFTWARE\NCH Software\Pixillion\Software\SVar
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\PixillionInstall
- HKEY_CURRENT_USER\SOFTWARE\NCH Software\Pixillion\Settings\InstalledByAdmin
- HKEY_CURRENT_USER\SOFTWARE\NCH Software\Pixillion\UsageStatsChoice\llinad
- HKEY_CURRENT_USER\SOFTWARE\NCH Software\Pixillion\Settings\InstallerPath
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NCH Software\Pixillion\Settings\InstallerPath
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.cab
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.exe
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchdata.cab
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchdata.dat
- C:\ProgramData\Packages\Microsoft.SkypeApp_kzf8qxf38zg5c\S-1-5-21-4005801669-2598574594-602355426-1001\SystemAppData\Helium\Cache\c4c43f2d3b8a6f97.dat
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.exe
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchdata.dat
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchdata.cab
- C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.cab
- C:\Users\<USER>\AppData\Local\Temp\n1s
- cversions.3.m
- Local\Shell.CMruPidlList
- Global\SyncRootManager
- Local\Mutexf01b4d95cf55d32a.automaticDestinations-ms
- Global\PixillionStarting
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 16c0719d8b35c94b61ab…f5c2f1Never scannednever seen before
- cd3d95863019e25960ad…f2c0d3Never scannednever seen before
- 3badeb53dd8fde1d5da3…d79e47Never scannednever seen before
- dee2497d9fab4c5df0b8…d4704fNever scannednever seen before
- 120aa0989e7cfbda2606…31293cNever scannednever seen before
- 8bc2a54f17b63b43fee5…3f4e0dNever scannednever seen before
- 979f9932fc766760a8dd…1a847fNever scannednever seen before
- e17a6beadd1a71207662…8399b6Never scannednever seen before
- 946ec5e46e155101da5a…73bccfNever scannednever seen before
- ee8b8e8567a4e9447406…d7dfa3Never 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.
- 6rule hits recorded
- 0 / 75engines flagged
- 593sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 593 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from NCH Software.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Pixillion.exe — 090808d2df9151a806654628c1dfaca9fd7c795a357f41eb7b0e913bb0993239
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\pixpsetup_x32_13.02.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.exe" -installer "C:\Users\<USER>\Desktop\pixpsetup_x32_13.02.exe" -instdata "C:\Users\<USER>\AppData\Local\Temp\n1s\nchdata.dat"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nchsetup.cab — C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.cab
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: nchsetup.exe — C:\Users\<USER>\AppData\Local\Temp\n1s\nchsetup.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: secure.nch.com.au — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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.
- Check_Wine
- PE_Digital_Certificate
- Sus_Obf_Enc_Spoof_Hide_PE
Sandbox flagged persistence indicators (registry Run keys / services / scheduled tasks).
EvidenceHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\PixillionInstallThe 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
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
- Pixillion.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: NCH Software
- Size
- 2.1 MB
- Last analyzed
- Oct 6, 2026, 6:36 PM UTC
090808d2df9151a806654628c1dfaca9fd7c795a357f41eb7b0e913bb0993239Safety & 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 Pixillion.exe safe?
What is Pixillion.exe?
How many antivirus engines detected Pixillion.exe?
Is Pixillion.exe digitally signed?
What is the SHA-256 hash of Pixillion.exe?
Is it safe to run Pixillion.exe?
How up to date is this analysis of Pixillion.exe?
Community
Member reviews and reports for this exact file hash.