File verdict·Decided by the MT AI Engine
Our call

Suspicious

Unsigned 14 KB UPX-packed EXE with 10 low-to-mid tier detections and no tier-1 consensus or sandbox hits.

nilage
Trust score45Caution
PMHE4
14.0 KB
4f43e41a86f05118a43cfd3270b5
Antivirus engines
10 of 74 flagged
Code signing
Unsigned
Age
First seen 17y ago
MT AI Engine · Verdict analysis

The reasoning behind this verdict

The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.

55%Confidence
Moderate
Reasoning

Ten engines reported malicious results, but none came from tier-1 vendors and the tier-1 family consensus field is empty. The binary is unsigned, small, and carries an UPX overlay tag, yet entropy analysis shows no high-entropy packed code and sandbox runs produced zero malicious indicators. Medium prevalence across 13 submissions over 16 years further weakens the case for active threat. These conflicting signals place the sample in the borderline mixed-signals category.

Key signals · 4

Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.

  1. engines.tier1Malicious=0 with 10 total malicious (Varist W32/Nilage.gen!GSA, Kingsoft malware.kb.b.879)

  2. signing.signed=false, prevalence.classification=medium, file.ageDays=6030

  3. behaviour.hasMaliciousSandboxVerdict=false, contactedHosts.maliciousHosts=null, droppedChildren.hasMaliciousChild=null

  4. peAnalysis.highEntropyCode=false, peAnalysis.likelyPacked=false, tags=[overlay,peexe,upx]

Points in its favour
  • Zero tier-1 detections
  • No sandbox malicious verdict
  • No malicious host contact
Points against
  • Unsigned executable
  • 10 engine detections including tier-2 labels
  • UPX overlay present
Recommended action

Treat the file as untrusted pending further sandbox or dynamic analysis; avoid execution until additional corroboration is obtained.

What this file does

What it attempted when executed in an isolated sandbox

  • Moderate concern: Obfuscates or packs its code to avoid detection.

Translated from the file's technical behaviour during analysis. It never ran on your device.

What to do now

We couldn't fully clear this file. Treat it with caution.

  1. Don't run it unless you're certain it came from a source you trust.

  2. Check where you got it — an email attachment or a random download link is a red flag.

  3. If you're unsure, delete it. You can always re-download a clean copy from the official source.

  4. If you're still unsure, scan it again in a day or two — detections often catch up on newer files.

Threat family attribution

nilage corroborated by 2 sources

  • VT (74 engines)
    nilage
  • MT AI Engine
    nilage
No researcher-database hits
External threat-intel sources were not collected for this scan.
Antivirus engine breakdown

10 detections across 74 engines

10 malicious0 suspicious64 clean
Tier-117 engines
0flag
Top commercial AVs (low FP rate)
Tier-240 engines
4flag
Mainstream engines with mixed FP rates
Low-trust17 engines
6flag
Heuristic / generic-AI engines (high FP rate)
Bkav
malicious
W32.Malware.31524CC3
Cylance
malicious
Unsafe
Google
malicious
Detected
Kingsoft
malicious
malware.kb.b.879
MaxSecure
malicious
Trojan.Malware.300983.susgen
Paloalto
malicious
generic.ml
SentinelOne
malicious
Static AI - Suspicious PE
Trapmine
malicious
malicious.high.ml.score
Varist
malicious
W32/Nilage.gen!GSA
VBA32
malicious
BScope.Trojan.Wacatac
Hash 4f43e41a86f0… cross-referenced against 74 AV engines via our AV network.
PE forensics

Section entropy & packers

Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.

ent 2.75Unpacked
Section entropy3 sections
(unnamed)
0.00
(unnamed)
7.82
(unnamed)
3.82
0.0Packed threshold 7.28.0
Prevalence

How widely this file has been seen

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
7
Moderate upload volume.
Total submissions
13
Includes repeat uploads by the same source.
First seen
17y ago
Jan 14, 2010
Prevalence quadrant
Rare · New
Targeted malware lives here
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Trusted legitimate binaries
File identity

Forensic fingerprint

File biography
First seen (VT)
1/14/2010, 6:38:31 AM
First seen (MalwareBazaar)
Last analysis (VT)
7/14/2026, 11:27:44 PM
Scanned here
7/19/2026, 2:57:36 AM
File name
PMHE4
Size
14.0 KB
MIME type
(unknown)
Detected type
Win32 EXE
SHA-256
4f43e41a86f05118a4f362e3cfe69df490c193d82c699a1e7d13353cfd3270b5
MD5
b3eada658ef11ddc1284a6e4ad66cf04
SHA-1
914268ce72b7b815393ba4bdce52a4b9662f3fb9
PE imphash
db0bad9f17d5c39211372ed6dff15a54
First seen (VT)
1/14/2010, 6:38:31 AM
Last analysis (VT)
7/14/2026, 11:27:44 PM
First scan (MalwareTips)
7/19/2026, 2:57:36 AM
Last scan (MalwareTips)
7/19/2026, 2:57:36 AM
Behavior tags
overlaypeexeupx
Frequently asked

Safety FAQ

Common questions about PMHE4, answered from the scan data above.

  • PMHE4 is suspicious — treat it as unsafe until you're sure. 10 of 74 antivirus engines flag it (family: nilage), which isn't a strong consensus but is enough to be cautious. Don't opened it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
  • PMHE4 is a file, about 14 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
  • 10 of 74 antivirus engines flagged PMHE4, 10 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
  • 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.
  • To remove PMHE4: 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 the original PMHE4 file and empty the Recycle Bin/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.
  • PMHE4 is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the nilage 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.
  • The SHA-256 hash of PMHE4 is 4f43e41a86f05118a4f362e3cfe69df490c193d82c699a1e7d13353cfd3270b5, and its MD5 is b3eada658ef11ddc1284a6e4ad66cf04. 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.
  • This report reflects the scan run on July 19, 2026. Because a file's hash never changes, the identity of PMHE4 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.
Community classification

Reviews & malware reports(0)

Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.

Loading…
Loading reports…
Files are processed in a streaming pass-through — MalwareTips never stores the binary on its servers. Only the scan result (hash, detections, verdict) is retained so the next person who scans the same file gets an instant answer. 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.