File scan report
Verdict Suspicious
Is EPlan License Manager. 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.
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
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
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
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
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
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
7 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 4 of the 68 antivirus engines that checked it raised detections, with no major consensus or confirmed family.
The antivirus evidence is limited: 4 of the 68 antivirus engines that checked it detected the file, none were major, and the labels do not form a reliable family consensus. Evidence from the test run is more concerning because the sample wrote to the Windows hosts file and mapped to T1055, T1134, and T1562.001. These actions can support process injection, privilege abuse, and impairment of security controls, although the sandbox did not issue an explicit malware finding. The executable is unsigned and has no established publisher history to explain these actions. No complete reputation check is available for the observed IP addresses and URL, leaving the network activity unresolved. The balance supports containment and further verification rather than execution.
What We Detected
Four of the 68 antivirus engines that checked it flagged the executable. Skyhigh used a behavior-based worm label and TrellixENS used the generic Artemis label, while no major antivirus engines detected it and no named family consensus formed.
Threat Behavior
One completed sandbox run recorded writes to the Windows hosts file and techniques T1055, T1134, and T1562.001. The sample also contacted multiple IP addresses and a URL, but no complete host-reputation cross-check is available. Ten dropped files were inspected without a confirmed malicious child, though their individual verdicts remain unknown.
What To Do Now
Do not execute the file on a production or personal system. Keep security software enabled, let your antivirus remove the executable, and obtain a fresh copy from EPLAN's official distribution or support channel if this license-management component is required.
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.
- No major antivirus engine detections among 74 engines
- No strong family consensus
- No explicit malicious sandbox verdict
- No confirmed malicious file it created
- No CIRCL, MalwareBazaar, or YARAify corroboration
- Unsigned Win32 executable with no signer history
- Modified the Windows hosts file
- Runtime mapping to process injection
- Runtime mapping to access-token manipulation
- Runtime mapping to impairment of defenses
- Multiple direct-IP contacts without a complete reputation cross-check
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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
EPlanLicenseManager.exe
eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\Desktop\program.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
<PATH_SAMPLE.EXE>
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
hosts
C:\Windows\System32\drivers\etc\hosts
Test run - Evidence 5 of 7: Written fileSeen in the test run
hosts
<DRIVERS>\etc\hosts
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
218.85.157.99
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
114.114.114.114
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
21MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1018
- T1027· Obfuscated code
- T1027.005· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1056· Keylogging
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1112
- T1129· Loads modules
- T1134
- T1140· Deobfuscation
- T1222
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1553
- T1553.004
- T1562.001· Disables security
Observed activity
Processes started
12Programs the file ran, with their command lines.
program.exe"C:\Users\<USER>\Desktop\program.exe"<PATH_SAMPLE.EXE>cmd.exe%WINDIR%\system32\cmd.exetaskhost.exe%WINDIR%\system32\taskhost.exeaudiodg.exe%WINDIR%\system32\audiodg.exesc.exe%WINDIR%\system32\sc.exe
Show all 12 entries for processes started
sppsvc.exe%WINDIR%\system32\sppsvc.exeaiwarje.exeC:\ctqtnbqo\aiwarje.exerundll32.exe%WINDIR%\system32\rundll32.exepujry.exeC:\hack\pujry.exezhrhscwu.exeC:\hdwwkvmj\zhrhscwu.exeeaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657.exe%SAMPLEPATH%\eaaeadc99545c88b1190d1a684ead9a0682cb5b622246395b40b1040ab9a5657.exe
Network contacts
33 hosts, listed as 2 addresses, 1 link. Links show the host and path only.
- IP address
218.85.157.99 - IP address
114.114.114.114 - URL
eplan.prod.sentinelcloud.com
Files
21Files the file created, changed or deleted.
- Written
C:\Windows\System32\drivers\etc\hosts - Written
<DRIVERS>\etc\hosts - Written
%WINDIR%\System32\drivers\etc\hosts - Written
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll - Written
\Device\ConDrv - Written
\Device\ConDrv\\Connect
Show all 21 entries for files
- Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1150.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER122B.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER125B.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A1.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B1.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER16C2.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB17.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERBC2.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF2.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER294D.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER295F.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER296F.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER347.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER49E.tmp.csv
Registry and auto-start
6Settings the file changed, including ways to start again after a restart.
- Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Object List - Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates\1F06C90B9C923BEF67259FC52C5EC00FB0C2C8E5
Sandbox background — not the file
16The analysis machine's own processes and connections, recorded in every run.
- VM process
conhost.exe<SYSTEM32>\conhost.exe - VM process
conhost.exe%WINDIR%\system32\conhost.exe - VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM host
23.216.147.76 - VM host
20.99.184.37 - VM host
20.99.133.109
Show all 16 entries for sandbox background — not the file
- VM host
192.229.211.108 - VM host
a83f:8110:0:0:700:700:2800:4000 - VM host
52.185.73.156 - VM host
23.213.37.172 - VM host
192.168.0.11 - VM host
151.101.22.172 - VM host
184.27.218.92 - VM host
a83f:8110:0:0:100:0:1800:0 - VM host
192.168.0.14 - VM host
8.8.8.8
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 49c23f0d6d2b5ec56b65…593bd8Not checkedno saved verdict
- daf4325b2d0685231504…b2c3ffNot checkedno saved verdict
- 2b2e4840057148fb8f12…735c28Not checkedno saved verdict
- 4b731c3ef6437c37fabf…441387Not checkedno saved verdict
- 42fb3f59bfdd779b4561…2d5b2eNot checkedno saved verdict
- f6314e18c79f99019bcd…1a1818Not checkedno saved verdict
- 6b7e52bfdad6c92eafdb…123a4dNot checkedno saved verdict
- 09eb644b936f1d9626ca…b53901Not checkedno saved verdict
- e6bcad118e4ae3326daf…9cffb1Not checkedno saved verdict
- 21cbbba46c592967f23e…ab946bNot checkedno saved verdict
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.
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
Antivirus consensus
4 of 68 engines flagged this file
6 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 4 detections come from 2 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-117 engines1flagged
- Tier-236 engines1flagged
- Low-trust15 engines2flagged
View all 74 engine results
- APEXMalicious: Malicious
- McAfeeDMalicious: ti!EAAEADC99545
- SkyhighMalicious: BehavesLike.Win32.Worm.vh
- TrellixENSMalicious: Artemis!86F54580357B
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureNo result
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrendMicroNo result
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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\hostsVirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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?
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.