MalwareTips
Threat LensFile scan report

Is SPHealthAnalyzer.exe safe?

Verdict
Malicious

Six tier-1 engines contribute to 22 of 74 detections, with multiple products independently identifying the Sliver offensive framework or related WinGo trojan code.

The strongest evidence is corroborated identification of Sliver by Sophos, Elastic, ZoneAlarm, and Microsoft, alongside WinGo detections from ESET-NOD32 and Ikarus. This unsigned, newly observed executable has no established publisher history, and no runtime analysis is available to reduce the concern.

Do not run this file

Do not execute this file; quarantine or delete it while keeping endpoint protection enabled. If it already ran, isolate the host and perform a full incident-response scan for remote-access activity and persistence.

Read the full analysis
Saved file evidenceAntivirus consensus
22of 74 flagged
Flagged 22No detection 52
Digital specimenSPHealthAnalyzer.exee63fd1bdac1d5df208…58f21c75c0cb5e
Size35.8 MB
Code signingUnsigned
SandboxPartial coverage
First seenToday
Evidence2 priority signals
22 of 74 antivirus engines flagged the file, including ALYac and Arcabit.

Recommended next actions

01

Before running

Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.

02

If you already ran it

Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

94%Confidence
Very high
Analyst conclusion

The strongest evidence is corroborated identification of Sliver by Sophos, Elastic, ZoneAlarm, and Microsoft, alongside WinGo detections from ESET-NOD32 and Ikarus. This unsigned, newly observed executable has no established publisher history, and no runtime analysis is available to reduce the concern.

Where this verdict could be wrong5 caveats
  • engines.tier1FamilyConsensus identifies WinGo from only 2 engines, so it does not meet the strong-consensus threshold.
  • Eight tier-1 engines did not detect the sample, including Avast, AVG, Avira, DrWeb, F-Secure, and Fortinet.
  • externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect intelligence coverage rather than benignity.
  • peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false conflict with several generic packed or obfuscated labels.
  • behaviour=null means the Sliver identification is not supported by completed runtime observation.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Do not execute this file; quarantine or delete it while keeping endpoint protection enabled. If it already ran, isolate the host and perform a full incident-response scan for remote-access activity and persistence.

Scan transparency

Coverage & freshness

3 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    22 of 74 engines flagged the file.

  • Sandbox

    Partial

    Runtime data is present, but no completed sandbox environment is recorded.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded

  • YARA

    Complete

    Rule evaluation completed with no recorded matches.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Threat context

How hacktools are abused

This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.

Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

This file is dangerous. Treat it as harmful and remove it.

  1. Recovery step 01

    Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.

  2. Recovery step 02

    If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.

  3. Recovery step 03

    If you typed any passwords while it was open, change them from a device you trust.

  4. Recovery step 04

    Get a fresh copy from the developer's official site or an official app store.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

8 evidence-based answers
Is SPHealthAnalyzer.exe a virus?
Evidence-based answer
Yes — SPHealthAnalyzer.exe is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 22 of 74 antivirus engines flag it (family: Sliver). It behaves as a hacktool — dual-use offensive tooling that is dangerous regardless of intent. If you've already run it, see the removal and recovery steps below.
What is SPHealthAnalyzer.exe?
Evidence-based answer
SPHealthAnalyzer.exe is a Windows executable program (application/x-msdownload), about 35.8 MB. Our analysis identifies it as malicious (family: Sliver) — a hacktool — dual-use offensive tooling that is dangerous regardless of intent. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
How many antivirus engines detected SPHealthAnalyzer.exe?
Evidence-based answer
22 of 74 antivirus engines flagged SPHealthAnalyzer.exe, 22 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
What should I do if I already ran SPHealthAnalyzer.exe?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove SPHealthAnalyzer.exe?
Evidence-based answer
To remove SPHealthAnalyzer.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What kind of malware is SPHealthAnalyzer.exe?
Evidence-based answer
SPHealthAnalyzer.exe is classified as a hacktool — dual-use offensive tooling that is dangerous regardless of intent. Engines attribute it to the Sliver family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
What is the SHA-256 hash of SPHealthAnalyzer.exe?
Evidence-based answer
The SHA-256 hash of SPHealthAnalyzer.exe is e63fd1bdac1d5df20888f31d8162524c2374ec72b3d4a736d658f21c75c0cb5e, and its MD5 is f8b2b83bdec324506dc3028ced2ad7ec. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of SPHealthAnalyzer.exe?
Evidence-based answer
This report reflects the scan run on September 15, 2026. Because a file's hash never changes, the identity of SPHealthAnalyzer.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scan another
Check a different file
URL instead?
Check if a link is safe
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.