File scan report

Verdict Suspicious

Analyzed , 1 month ago

Is EPlanLicenseManager.exe safe? Treat it as suspicious.

The unsigned executable modified the Windows hosts file and exhibited injection and defense-evasion techniques, outweighing its limited, non-major antivirus engine detections.

Read the whole reasonShow less

Why Suspicious? 4 antivirus engines flag it and one of our detection rules matched it.

Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.

Don't run it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

4 of 68 flagged

  • Flagged 4
  • No detection 64
  • No result 6
FileEPlanLicenseManager.exe2.3 MBSHA-256 eaaeadc99545…9a5657
  • Code signing Unsigned
  • Test run Completed
  • First seen 5y ago
1 strong detection rule matched this file.

Chapter 02

Why we think so

7 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Only 4 of the 68 antivirus engines that checked it raised detections, with no major consensus or confirmed family.

Where this verdict could be wrong4 caveats
  • No sandbox returned a malicious verdict, so the completed sandbox did not issue an explicit malware finding.
  • No dropped file is known to be malicious, although all 10 child verdicts are unknown.
  • The absence of community YARA matches, the absence of a known-software database match, and the absence of a MalwareBazaar listing provide no researcher-curated corroboration.
  • The absence of packing indicators and the absence of packed-level code entropy reduce concern about static packing or code obfuscation.

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

6 sources checked · 5 complete · 1 partial. 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
  • 21sandbox rule tags
  • 12spawned processes
  • 3network contacts
  • 21filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Used an unusual way to talk to a server.

  • Moderate concern: Unpacked hidden content while it ran.

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Talked to servers over the internet during the test run.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

  • Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      EPlanLicenseManager.exe

      eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      program.exe

      "C:\Users\<USER>\Desktop\program.exe"

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      <PATH_SAMPLE.EXE>

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      hosts

      C:\Windows\System32\drivers\etc\hosts

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      hosts

      <DRIVERS>\etc\hosts

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      218.85.157.99

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      114.114.114.114

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

4 of the 68 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompleteRisk signal: 4 of 68 engines flagged it · 6 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial3 hosts contacted in the test run had no completed reputation check Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 2 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 4

  • TrellixENS (major engine)Artemis!86F54580357B
  • APEXMalicious
  • McAfeeDti!EAAEADC99545
  • SkyhighBehavesLike.Win32.Worm.vh

File fingerprint

Last analyzed
Sep 20, 2026, 2:06 PM UTC
SHA-256
eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657
SHA-1
661b318b8a8e8121532976e9e28dc7660a3cbb40
MD5
86f54580357b4d9d87177d3aaae1b959

About this file

EPlanLicenseManager.exe is a Win32 EXE file of 2.3 MB.

Type and size
Win32 EXE · 2.3 MB
Signer
UnsignedNo code signature.
First seen
Apr 20, 2021On VirusTotal.
Submitted by
75 distinct sources
Packer
None detected
Entropy
6.60 of 8

First scanned Updated

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is EPlanLicenseManager.exe safe, or is it malware?
EPlanLicenseManager.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 4 of the 68 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is EPlanLicenseManager.exe?
EPlanLicenseManager.exe is a Windows program, about 2.3 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Apr 20, 2021.
How many antivirus engines detected EPlanLicenseManager.exe?
4 of the 68 antivirus engines that checked it flag EPlanLicenseManager.exe, including Trellix (McAfee) and APEX. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran EPlanLicenseManager.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of EPlanLicenseManager.exe?
The SHA-256 fingerprint of EPlanLicenseManager.exe is eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657, and its MD5 is 86f54580357b4d9d87177d3aaae1b959. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of EPlanLicenseManager.exe?
This report reflects the scan on Sep 20, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.