Is Retrac_3.0.10_x64_en-US.msi safe?
No antivirus engine detected this signed, widely submitted installer, while the isolated sandbox heuristics lack direct evidence of credential theft or injection.
The installer drew no detections from 75 antivirus engines, including all 17 tier-1 engines, and carries a verified Lezah Limited signature. One sandbox produced process-injection and credential-access heuristics, but no malicious sandbox conclusion or direct evidence confirms those actions.
25f0be55e185fa99ff…de629d9e26f59cRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 installer drew no detections from 75 antivirus engines, including all 17 tier-1 engines, and carries a verified Lezah Limited signature. One sandbox produced process-injection and credential-access heuristics, but no malicious sandbox conclusion or direct evidence confirms those actions.
No engine among 75 detected the installer, and all 17 tier-1 engines were silent. The file is signed with a verified Lezah Limited certificate and has already appeared from 595 sources across 683 submissions. A prior version with the same signer also received a benign assessment, although the signer history consists of only one comparable sample. The sandbox mapped activity to T1055 and raised an LSASS-related heuristic, but its saved evidence only identifies ordinary Windows process entries and did not produce a malicious runtime conclusion. No malicious child was recorded, and no complete host-reputation check is available because no contacted-host result was saved.
What We Detected
None of 75 antivirus engines flagged the MSI, including 17 tier-1 engines. The installer has a verified signature from Lezah Limited and was submitted 683 times by 595 sources within five days, indicating broad distribution. A prior Retrac 3.0.9 installer matched by the same signer also received a benign assessment.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055 and raised a credential-access heuristic involving LSASS. However, the retained evidence lists Windows processes rather than demonstrating memory reads or process injection, and the sandbox did not issue a malicious conclusion. No dropped file hashes, persistence indicators, domains, IP addresses, or URLs were recorded. A complete contacted-host reputation result was not saved.
What To Do Now
Use the installer only if it came from the expected official distribution channel and its Lezah Limited signature remains valid. Keep endpoint protection enabled and rescan if the signature changes or installation produces unexpected credential prompts, process access, or network traffic.
Where this verdict could be wrong3 caveats
- The sandbox mapped activity to MITRE T1055 and the MalwareTips.Synth.CredentialDumper heuristic associated a listed lsass.exe process with possible credential access; the recorded process names do not independently prove either action.
- signing.signerStats.totalSamples=1 and signing.trustedPublisher.matched=false, so the verified certificate has only a very limited established history.
- contactedHosts=null, although no domains, IPs, or URLs were recorded in the completed sandbox run.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines detected the sample.
- All 17 tier-1 engines reported no detection.
- The Lezah Limited digital signature is verified.
- 595 sources submitted the file 683 times.
- A prior same-signer Retrac installer was assessed as benign.
- Sandbox mapping includes MITRE T1055.
- An LSASS-related credential-access heuristic fired.
- The verified signer has only 1 historical sample.
- No complete contacted-host reputation result is available.
Confirm the installer came from the expected official source and verify the Lezah Limited signature before running it. Keep endpoint protection enabled and investigate any unexpected credential-access alerts during installation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 5MITRE ATT&CK techniques
- 9spawned processes
- 0network contacts
- 8filesystem & mutex artifacts
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
Retrac_3.0.10_x64_en-US.msi
25f0be55e185fa99ffa1796f2e7ade2c121cbb1fb945dde1ffde629d9e26f59c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Retrac_3.0.10_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis - Written fileObserved
MSIb0ac3.tmp
C:\MSIb0ac3.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\MSIb0ac3.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Windows\Fonts
- C:\MSIb0ac3.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:2428:304:WilStaging_02
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
- 0 / 75engines flagged
- 595sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from Lezah Limited.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: Retrac_3.0.10_x64_en-US.msi — 25f0be55e185fa99ffa1796f2e7ade2c121cbb1fb945dde1ffde629d9e26f59c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Retrac_3.0.10_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: MSIb0ac3.tmp — C:\MSIb0ac3.tmp
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\System32\svchost.exe -k NetworkService -pSandbox 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
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- Retrac_3.0.10_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Lezah Limited
- Size
- 14.4 MB
- Last analyzed
- Sep 22, 2026, 7:24 AM UTC
25f0be55e185fa99ffa1796f2e7ade2c121cbb1fb945dde1ffde629d9e26f59cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Retrac_3.0.10_x64_en-US.msi safe?
What is Retrac_3.0.10_x64_en-US.msi?
How many antivirus engines detected Retrac_3.0.10_x64_en-US.msi?
Is Retrac_3.0.10_x64_en-US.msi digitally signed?
What is the SHA-256 hash of Retrac_3.0.10_x64_en-US.msi?
Is it safe to install Retrac_3.0.10_x64_en-US.msi?
How up to date is this analysis of Retrac_3.0.10_x64_en-US.msi?
Community
Member reviews and reports for this exact file hash.