Is EzExtractSetup.exe safe?
A verified, widely distributed installer has limited antivirus detections, but observed LSASS targeting and process-injection indicators warrant caution pending publisher verification.
Only 2 of 74 engines flagged the installer, and most high-trust engines did not corroborate the Chimera or MulDrop28 labels. However, one runtime analysis recorded process-injection indicators and LSASS targeting, so the valid signature and broad prevalence are insufficient to dismiss the risk.
4704846c5605552a25…b36a27cae6800fRecommended 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.
Only 2 of 74 engines flagged the installer, and most high-trust engines did not corroborate the Chimera or MulDrop28 labels. However, one runtime analysis recorded process-injection indicators and LSASS targeting, so the valid signature and broad prevalence are insufficient to dismiss the risk.
DrWeb and Gridinsoft flagged the sample, but only DrWeb supplies a high-trust vote and there is no strong family consensus. The file is verified-signed by Empire Security Services Inc and has been submitted thousands of times, which weighs against a straightforward ransomware interpretation. Conversely, the completed runtime analysis mapped activity to T1055 and reported interaction with LSASS, both unusual for an archive-extraction installer. The same run did not produce a malicious sandbox verdict, and none of ten inspected children was identified as malicious, although their individual verdicts remained unknown. Domain coverage found no cached malicious or suspicious domains, but the broader set of contacted IPs was not fully covered. The conflicting engine, runtime, signer, and prevalence evidence supports caution rather than a definitive family attribution.
What We Detected
Two of 74 antivirus engines flagged the installer. DrWeb identified MulDrop28, while Gridinsoft used a Chimera ransomware label; the other 16 reporting tier-1 engines did not flag it, so the family attribution lacks strong independent agreement.
Threat Behavior
One completed runtime analysis mapped activity to T1055 process injection and T1562.001 defense impairment, and a heuristic reported targeting of lsass.exe. Those actions are security-sensitive and atypical for a file-extraction installer. However, that run did not issue a malicious sandbox verdict, no inspected child was identified as malicious, and the observed installer activity included writing application files and registering shell-extension DLLs.
Trust and Reputation
The executable has a verified signature from Empire Security Services Inc, but the publisher is not on the curated trusted list and has no established sample history. The file is more than two years old and has 3,247 submitters across 5,263 submissions. The observed domains were fully checked and had no cached malicious or suspicious results, but contacted IPs were not comprehensively covered.
What To Do Now
Do not run the file unless its hash and signature can be matched to the publisher's official release channel. Keep endpoint protection enabled, and if execution is necessary, use an isolated test environment rather than a production system.
Where this verdict could be wrong5 caveats
- Only 2/74 engines detected the file, and tier1FamilyConsensus has just one engine for muldrop28 rather than strong agreement.
- behaviour.hasMaliciousSandboxVerdict=false, although one completed run cannot exclude environment-sensitive activity.
- droppedChildren inspected 10 files and found no malicious child, but all 10 child verdicts remained unknown.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false; absence of hits can reflect coverage gaps.
- The file is verified-signed and widely submitted, which conflicts with the isolated Chimera and MulDrop28 labels.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The executable has a verified code signature.
- Only 2/74 engines flagged the sample.
- Sixteen of 17 reporting tier-1 engines did not flag it.
- The file has 3,247 submitters and 5,263 submissions.
- No malicious child was identified among 10 inspected files.
- DrWeb detected Trojan.MulDrop28.6828.
- Gridinsoft detected Ransom.Win32.Chimera.tr.
- Runtime evidence includes T1055 process injection.
- The CredentialDumper heuristic cites lsass.exe targeting.
- T1562.001 indicates possible impairment of defenses.
- Empire Security Services Inc has no established signer history.
Obtain the installer only from the publisher's official channel and verify SHA-256 4704846c5605552a2573aeb62f176630fd2ba5498457420c3fb36a27cae6800f before use. Keep endpoint protection enabled and avoid execution on sensitive systems until the LSASS-related behavior is independently explained.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial8 of 28 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 33MITRE ATT&CK techniques
- 15spawned processes
- 30network contacts
- 36filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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
EzExtractSetup.exe
4704846c5605552a2573aeb62f176630fd2ba5498457420c3fb36a27cae6800f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nshD070.tmp
C:\Users\<USER>\AppData\Local\Temp\nshD070.tmp
04Isolated runtime analysis - Written fileObserved
NsisPlugin.dll
C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\NsisPlugin.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
ezextractinstaller.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
x1.c.lencr.org
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.
- ezextractinstaller.com
- x1.c.lencr.org
- www.microsoft.com
- res.public.onecdn.static.microsoft
- c.pki.goog
- pki-goog.l.google.com
- windows.msn.com-ion.edgesuite.net
- a1672.dscr.akamai.net
- 172.67.181.227
- 192.168.0.5
- 23.32.75.5
- 23.218.185.6
- 52.185.73.156
- 23.216.81.152
- 192.168.0.66
- 104.21.32.2
- 151.101.22.172
- 184.31.197.9
- http://c.pki.goog/r/gsr1.crl
- http://c.pki.goog/r/r4.crl
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\EzExtractPro\InstallPath
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\EzExtractPro\DisplayName
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\EzExtractPro\InstallDate
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\EzExtractPro\InstallLocation
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\EzExtractPro\DisplayIcon
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\EzExtractPro\DisplayVersion
- C:\Users\<USER>\AppData\Local\Temp\nshD070.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\NsisPlugin.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\INetC.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\INetC.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\NsisPlugin.dll
- C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\System.dll
- EzExtractorProSetup
- cversions.3.m
- \Sessions\1\BaseNamedObjects\EzExtractorProSetup
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
- \Sessions\1\BaseNamedObjects\Local\__DDrawExclMode__
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ac3706ebbb78cfba74e5…0aba8fNever scannednever seen before
- 23abc9395b36419700f3…728298Never scannednever seen before
- 56b96add1978b1abba28…753fe2Never scannednever seen before
- d79bf7ffb02666fb8644…c1fcecNever scannednever seen before
- a05db3b6ad708ea1c1ab…ac4224Never scannednever seen before
- 8dc562cda7217a3a52db…7f65a8Never scannednever seen before
- 85e03805f90f72257dd4…1dccb9Never scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never scannednever seen before
- b33efcb95235b98b4850…29307fNever scannednever seen before
- 554ef8f1d2b201421a53…c11f5eNever 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.
- 2rule hits recorded
- 2 / 74engines flagged
- 3,247sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
2 of 74 antivirus engines flagged the file, including DrWeb and Gridinsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,247 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: EzExtractSetup.exe — 4704846c5605552a2573aeb62f176630fd2ba5498457420c3fb36a27cae6800f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nshD070.tmp — C:\Users\<USER>\AppData\Local\Temp\nshD070.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: NsisPlugin.dll — C:\Users\<USER>\AppData\Local\Temp\nsxD081.tmp\NsisPlugin.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: ezextractinstaller.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: x1.c.lencr.org — 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.
The 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.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
2 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- EzExtractSetup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Empire Security Services Inc
- Size
- 4.4 MB
- Last analyzed
- Oct 1, 2026, 8:44 PM UTC
4704846c5605552a2573aeb62f176630fd2ba5498457420c3fb36a27cae6800fSafety & 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 EzExtractSetup.exe safe, or is it malware?
What is EzExtractSetup.exe?
How many antivirus engines detected EzExtractSetup.exe?
What should I do if I already ran EzExtractSetup.exe?
How do I remove EzExtractSetup.exe?
Is EzExtractSetup.exe digitally signed?
What is the SHA-256 hash of EzExtractSetup.exe?
How up to date is this analysis of EzExtractSetup.exe?
Community
Member reviews and reports for this exact file hash.