Is PoeEnhancer.exe safe?
Only Symantec flagged this unsigned, newly observed executable with a generic machine-learning label, while 16 other tier-1 engines reported no detection.
Symantec is the only one of 74 engines to flag the executable, using a generic machine-learning label rather than a named family. Most high-trust engines found nothing, but the file is unsigned, newly observed, and lacks runtime evidence, so it should not be trusted without source verification.
277d4be20d67fe5da0…fd095d1877adc5Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Symantec is the only one of 74 engines to flag the executable, using a generic machine-learning label rather than a named family. Most high-trust engines found nothing, but the file is unsigned, newly observed, and lacks runtime evidence, so it should not be trusted without source verification.
The scan produced one detection among 74 engines, and Symantec supplied the generic label ML.Attribute.HighConfidence. Sixteen other tier-1 engines reported no detection, and no tier-1 family consensus exists. This pattern has a substantial false-positive possibility, reinforced by the absence of external intelligence matches. However, the executable is unsigned and has only one recorded submission, leaving its publisher and reputation unestablished. No completed sandbox observation or complete contacted-host reputation result is available, so execution and network activity cannot be assessed. These mixed signals justify caution rather than treating the lone detection as confirmed malware or dismissing it outright.
What We Detected
Symantec was the only one of 74 engines to flag the file, reporting the generic machine-learning label ML.Attribute.HighConfidence. Sixteen other tier-1 engines reported no detection, and there is no corroborated family consensus. External checks returned no CIRCL, MalwareBazaar, or YARAify match, although absence from those sources does not prove the file is benign.
Threat Behavior
No completed sandbox run is available, so no runtime behavior was observed. The contacted-host reputation check was also unavailable, meaning there is no complete result for possible network contacts. Static PE analysis found no likely packing or high-entropy code, but the executable is unsigned and newly observed.
What To Do Now
Do not run the file unless it came directly from the developer's official release channel and its SHA-256 value can be independently verified. Keep endpoint protection enabled and consider testing it in an isolated environment after obtaining publisher confirmation.
Where this verdict could be wrong3 caveats
- Symantec, a tier-1 engine, reported ML.Attribute.HighConfidence, so the detection cannot be dismissed as low-trust noise.
- The file is unsigned and has only one recorded submission, limiting confidence in a benign interpretation.
- Four of five similarHashes entries were previously safe, but matchKind=filetype is too broad to establish that this executable shares their provenance.
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/74 engines reported a detection
- 16 tier-1 engines reported no detection
- No strong tier-1 family consensus
- externalIntel.yaraify.ruleCount=0
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- Symantec tier-1 detection: ML.Attribute.HighConfidence
- Unsigned Win32 executable
- Only one source and one recorded submission
- No completed sandbox observation
- No complete contacted-host reputation result
Verify SHA-256 277d4be20d67fe5da002aff81ef467ecc16954f8e767b4ee8ffd095d1877adc5 through the developer's official release channel before use. Keep endpoint protection enabled and avoid execution if provenance cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 1 / 74engines 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 of 74 antivirus engines flagged the file, including Symantec.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 of 74 engines flagged this file
View all 74 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. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- PoeEnhancer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 24.8 MB
- Last analyzed
- Sep 17, 2026, 8:38 PM UTC
277d4be20d67fe5da002aff81ef467ecc16954f8e767b4ee8ffd095d1877adc5Safety & 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 run 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 developer's official site or an official app store.
- 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 PoeEnhancer.exe safe, or is it malware?
What is PoeEnhancer.exe?
How many antivirus engines detected PoeEnhancer.exe?
What should I do if I already ran PoeEnhancer.exe?
How do I remove PoeEnhancer.exe?
What is the SHA-256 hash of PoeEnhancer.exe?
How up to date is this analysis of PoeEnhancer.exe?
Community
Member reviews and reports for this exact file hash.