File scan report
Verdict Safe
Is nvidia
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
Includes the sandbox verdicts, 19 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 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.
Includes every engine result (75), 9 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 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.