File scan report
Verdict Safe
Is nvidia Profile Inspector. exe safe? Yes, no threats found.
Only MaxSecure flagged this widely submitted executable, while major antivirus engines remained silent and the combined sandbox summary found no corroborating high-risk activity.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 71 flagged
- Flagged 1
- No detection 70
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
One of the 71 antivirus engines that checked it flagged the executable with a generic trojan label, while no major antivirus engines detected it. The combined sandbox verdict was clean, and the file showed neither a named injection target nor sample-attributed network activity; the isolated community-rule match remains a caution rather than corroboration.
Only 1 of the 71 antivirus engines that checked it flagged the executable, and that result came from MaxSecure with a generic label rather than a named malware family. None of the major antivirus engines detected it, making the isolated alert likely to be a false positive. The combined sandbox verdict was clean, with no named process-injection target or sample-attributed network contact. One malware-associated community rule matched, but no antivirus consensus, runtime fact, or available static examination corroborated it. The file is unsigned, which weakens publisher assurance, but its 823-source prevalence and lack of stronger hostile evidence favor benign software.
What We Detected
MaxSecure was the only engine to flag the executable, using a generic trojan label. None of the major antivirus engines detected it, and no real malware family was identified.
Threat Behavior
The combined sandbox verdict was clean. No named process-injection target, persistence indicator, dropped file, or sample-attributed network connection was recorded. One community rule associated with obfuscated PowerShell matched, but the available evidence from the test run did not corroborate that lead.
What To Do Now
The isolated detection is most consistent with a false positive. Because the executable is unsigned and our static examination was unavailable, obtain it from the project's official release channel and keep security software enabled while running it.
Where this verdict could be wrong3 caveats
- One community rule, Detect_PowerShell_Obfuscation, matched a malware-associated pattern, although no engine consensus or evidence from the test run corroborated it.
- The executable is unsigned, so its publisher identity cannot be authenticated.
- Our static analysis was not available, leaving the community-rule match unverified against the uploaded bytes.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 71 antivirus engines that checked it flagged the executable, and no major antivirus engines detected it.
- The combined sandbox verdict was clean and showed no named process-injection target.
- The observed contact was identified as analysis-environment background traffic, and the complete host check found no known hostile destination.
- The file was submitted 989 times by 823 sources without broad detection consensus.
- No packing or unusually high-entropy code was found.
- The executable is unsigned, so there is no authenticated publisher identity.
- One community rule associated with obfuscated PowerShell matched the file.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 19sandbox rule tags
- 1spawned processes
- 0network contacts
- 7filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
19MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1027· Obfuscated code
- T1033· Reads user info
- T1036
- T1057· Lists programs
- T1059· Runs commands
- T1070· Covers its tracks
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1087
- T1129· Loads modules
- T1140· Deobfuscation
- T1497· Sandbox evasion
- T1553.005
- T1562.001· Disables security
- T1620· In-memory loading
Observed activity
Processes started
1Programs the file ran, with their command lines.
software.exe"C:\Users\user\Desktop\software.exe"
Files
3Files the file created, changed or deleted.
- Written
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser - Written
C:\Users\user\AppData\Local\nvidiaProfileInspector - Written
C:\Users\user\AppData\Roaming
Registry and auto-start
2Settings the file changed, including ways to start again after a restart.
- Set
HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Direct3D\MostRecentApplication\Name - Set
HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
Mutexes
4Named locks a program uses so only one copy runs; malware families often reuse them.
nvidiaProfileInspector\Sessions\1\BaseNamedObjects\nvidiaProfileInspector\Sessions\1\BaseNamedObjects\Local\__DDrawExclMode__\Sessions\1\BaseNamedObjects\Local\__DDrawCheckExclMode__
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
assets.msn.com
Chapter 04
Technical details
1 of the 71 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
The saved verdict treats these detections as likely false positives.
- MaxSecureTrojan.Malware.300983.susgen
File fingerprint
- Last analyzed
- Oct 11, 2026, 2:21 AM UTC
- SHA-256
071f38bfeec4fab0a33261f7fa010940e2c3c96fb21f03d18d490110ddb90b03- SHA-1
285091a7f88b98773aec95d0f9d1045f5dbd00f9- MD5
6074076c3b227845a5156eeec4b8d7ac
About this file
nvidiaProfileInspector.exe is a Win32 EXE file of 1.0 MB.
- Type and size
- Win32 EXE · 1.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 16, 2026On VirusTotal.
- Submitted by
- 823 distinct sources
- Packer
- None detected
- Entropy
- 6.19 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
1 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines1flagged
View all 75 engine results
- MaxSecureMalicious: Trojan.Malware.300983.susgen
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
- Detect_PowerShell_Obfuscation
- Skystars_Malware_Imphashgeneric
- VECT_Ransomwaregeneric
- win_rat_genericgeneric
- win_stealer_genericgeneric
- win32_dotnet_loadergeneric
- NETgeneric
- pe_imphashgeneric
- Sus_CMD_Powershell_Usagegeneric
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 uploaded, but first seen within the last six months. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is nvidiaProfileInspector.exe safe?
What is nvidiaProfileInspector.exe?
How many antivirus engines detected nvidiaProfileInspector.exe?
What is the SHA-256 hash of nvidiaProfileInspector.exe?
Is it safe to run nvidiaProfileInspector.exe?
How up to date is this analysis of nvidiaProfileInspector.exe?
Community
Member reviews and reports for this exact file hash.