Is EPlanLicenseManager.exe safe?
Only 4 of 76 engines detected the unsigned executable, but observed hosts-file modification and offensive techniques T1055, T1134, and T1562.001 warrant caution.
The executable has limited antivirus support for a threat finding: 4 of 76 engines flagged it, and no tier-1 engine identified malware. However, a completed sandbox recorded hosts-file modification plus process-injection, token-manipulation, and defense-evasion mappings, making execution risky until the file's source and purpose are verified.
eaaeadc99545c88b11…0b1040ab9a5657Recommended 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.
The executable has limited antivirus support for a threat finding: 4 of 76 engines flagged it, and no tier-1 engine identified malware. However, a completed sandbox recorded hosts-file modification plus process-injection, token-manipulation, and defense-evasion mappings, making execution risky until the file's source and purpose are verified.
Four of 76 engines flagged the sample, but all 17 reporting tier-1 engines were undetected and no malware family consensus formed. The completed sandbox nevertheless recorded a write to the Windows hosts file and mapped activity to T1055, T1134, and T1562.001. Those actions can interfere with networking, manipulate process context, or impair security controls, although technique mappings alone do not prove malicious intent. The executable is unsigned and has no established publisher history, reducing confidence in its claimed purpose. No malicious child, researcher-rule match, or curated intelligence hit corroborated the detections, and no complete host-reputation result is available for its observed contacts.
What We Detected
Four of 76 antivirus engines flagged the executable. Skyhigh used a behavioral worm label, TrellixENS reported an Artemis heuristic, VBA32 suggested a generic downloader, and APEX returned a generic malicious result. No tier-1 engine detected it, and the labels do not converge on a specific family.
Threat Behavior
A completed sandbox recorded writes to the Windows hosts file and mapped activity to T1055 process injection, T1134 access-token manipulation, and T1562.001 impairment of defenses. These are significant risk indicators, though the sandbox itself did not issue a malicious verdict. Multiple external IP contacts and one URL were observed, but the host-reputation cross-check was not completed or saved, so their reputation cannot be assessed here.
What To Do Now
Do not run the file on a production system until its origin and hash are verified through the official software vendor or an authorized administrator. Keep endpoint protection enabled, quarantine the executable if it arrived unexpectedly, and inspect the Windows hosts file if it has already been executed.
Where this verdict could be wrong5 caveats
- All 17 reporting tier-1 engines were undetected, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet.
- behaviour.hasMaliciousSandboxVerdict=false; the sandbox recorded concerning techniques but did not issue a malicious verdict.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children remained unclassified rather than confirmed benign.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false.
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- All 17 reporting tier-1 engines were undetected.
- No strong engine family consensus was present.
- No completed sandbox issued a malicious verdict.
- None of the 10 inspected dropped children was identified as malicious.
- No CIRCL, MalwareBazaar, or YARAify corroboration was found.
- Sandbox recorded modification of the Windows hosts file.
- Offensive technique mappings include T1055, T1134, and T1562.001.
- The Win32 executable is unsigned and has no signer history.
- Four antivirus engines produced generic or behavioral detections.
- Observed network contacts lack a complete host-reputation cross-check.
Quarantine the file and verify it against an official vendor-provided hash or installer before use. If it already ran, keep protection enabled and review the hosts file, running processes, and endpoint logs.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial16 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 21MITRE ATT&CK techniques
- 15spawned processes
- 16network contacts
- 21filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
EPlanLicenseManager.exe
eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
<PATH_SAMPLE.EXE>
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
hosts
C:\Windows\System32\drivers\etc\hosts
04Isolated runtime analysis - Written fileObserved
hosts
<DRIVERS>\etc\hosts
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.216.147.76
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.184.37
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 23.216.147.76
- 20.99.184.37
- 20.99.133.109
- 192.229.211.108
- a83f:8110:0:0:700:700:2800:4000
- 52.185.73.156
- 23.213.37.172
- 192.168.0.11
- 151.101.22.172
- 184.27.218.92
- eplan.prod.sentinelcloud.com
- C:\Windows\System32\drivers\etc\hosts
- <DRIVERS>\etc\hosts
- %WINDIR%\System32\drivers\etc\hosts
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
- \Device\ConDrv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1150.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER122B.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER125B.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A1.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B1.tmp.csv
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 49c23f0d6d2b5ec56b65…593bd8Never scannednever seen before
- daf4325b2d0685231504…b2c3ffNever scannednever seen before
- 2b2e4840057148fb8f12…735c28Never scannednever seen before
- 4b731c3ef6437c37fabf…441387Never scannednever seen before
- 42fb3f59bfdd779b4561…2d5b2eNever scannednever seen before
- f6314e18c79f99019bcd…1a1818Never scannednever seen before
- 6b7e52bfdad6c92eafdb…123a4dNever scannednever seen before
- 09eb644b936f1d9626ca…b53901Never scannednever seen before
- e6bcad118e4ae3326daf…9cffb1Never scannednever seen before
- 21cbbba46c592967f23e…ab946bNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 4 / 76engines flagged
- 72sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
4 of 76 antivirus engines flagged the file, including APEX and Skyhigh.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 84 times from 72 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: EPlanLicenseManager.exe — eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — <PATH_SAMPLE.EXE>
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: hosts — C:\Windows\System32\drivers\etc\hosts
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: hosts — <DRIVERS>\etc\hosts
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.147.76 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
Sample wrote to the Windows hosts file. Used to block AV update domains, redirect legit sites to phishing clones, or pin C2 by DNS override. Near-zero legit reason for a non-admin app to touch this file.
EvidenceC:\Windows\System32\drivers\etc\hostsThe saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence%WINDIR%\system32\rundll32.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence23.216.147.76 · 20.99.184.37 · 20.99.133.109
4 of 76 engines flagged this file
View all 76 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- EPlanLicenseManager.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.2 MB
- Last analyzed
- Sep 8, 2026, 6:05 PM UTC
eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657Safety & 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 EPlanLicenseManager.exe safe, or is it malware?
What is EPlanLicenseManager.exe?
How many antivirus engines detected EPlanLicenseManager.exe?
What should I do if I already ran EPlanLicenseManager.exe?
How do I remove EPlanLicenseManager.exe?
What is the SHA-256 hash of EPlanLicenseManager.exe?
How up to date is this analysis of EPlanLicenseManager.exe?
Community
Member reviews and reports for this exact file hash.