Our call: Is LTK.Manager_1.13.2_x64_en-US.msi safe?Suspicious
Newly submitted signed MSI shows sandbox process-injection and LSASS activity but zero engine detections.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 0 of 75 antivirus engines flagged the file.Observed · Antivirus analysis
- The file has a valid code signature from Natoken LLC.Observed · Code-signing metadata
98fa33f272f6e60254…fe96a16fbeRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
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
LTK.Manager_1.13.2_x64_en-US.msi
98fa33f272f6e602546dd973c91f87a6ac09dc3cde2a9f0e6a8d94fe96a16fbe
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\LTK.Manager_1.13.2_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
MSI60f5.tmp
C:\MSI60f5.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Natoken LLC.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: LTK.Manager_1.13.2_x64_en-US.msi — 98fa33f272f6e602546dd973c91f87a6ac09dc3cde2a9f0e6a8d94fe96a16fbe
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\LTK.Manager_1.13.2_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: MSI60f5.tmp — C:\MSI60f5.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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 file is a one-day-old Windows Installer signed by an unknown publisher. Sandbox evidence maps to process injection and LSASS access, yet no antivirus engine flagged it and no malicious verdict was returned from the sandbox run.
Zero detections across 75 engines and the absence of a tier-1 family consensus indicate the sample is not widely recognized as malware. However, the sandbox recorded MITRE techniques T1055 and T1562.001 plus LSASS interaction, which are offensive behaviours not typical of ordinary installers. The signer 'Natoken LLC' has no prior history in our database, so the certificate provides no reputation anchor. Because the contacted-host reputation check is missing, the single direct-IP connection cannot be assessed. These conflicting signals place the file in a borderline category that warrants caution.
What We Detected
75 engines scanned the MSI; none returned a malicious or suspicious result. The installer is digitally signed by 'Natoken LLC', but the publisher has no recorded history. Sandbox execution captured process activity consistent with T1055 (process injection) and T1562.001 (impair defenses) plus direct access to lsass.exe.
Threat Behavior
The observed techniques suggest the installer may attempt to inject into other processes or tamper with security settings. No malicious child processes were dropped and no sandbox verdict labeled the run malicious. Network activity was limited to a single direct IP with no domain context.
What To Do Now
Do not run the installer on production systems until additional reputation data or updated engine coverage is available. Keep endpoint protection enabled and consider executing the file only in an isolated test environment with enhanced monitoring.
Where this verdict could be wrong2 caveats
- If the sandbox mappings to T1055 and LSASS access are accurate, the file exhibits behaviour that legitimate installers rarely need; however, zero engine detections and no malicious sandbox verdict keep the evidence mixed.
- contactedHosts is null, so the single direct-IP contact (162.159.36.2) cannot be definitively classified as clean or malicious.
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 engines flagged the file
- No malicious sandbox verdict returned
- No dropped malicious children
- Sandbox mapped T1055 and T1562.001
- LSASS access observed
- Signer has no prior history
- File is only 1 day old
Treat the installer as untrusted until further reputation signals appear; run only in a controlled lab environment with active monitoring.
Behavior
Plain-English impact first, then the observed runtime evidence.
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 removable-media replication behaviour that can spread files between devices.
High concern: Attempted to impair or bypass security controls.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 1 server during sandbox analysis.
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.
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.
- 162.159.36.2
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\MSI60f5.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Windows\Fonts
- C:\MSI60f5.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:6764:304:WilStaging_02
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.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.
Evidence162.159.36.2
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- LTK.Manager_1.13.2_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Natoken LLC
- Size
- 13.7 MB
- Last analyzed
- Aug 1, 2026, 9:17 PM UTC
98fa33f272f6e602546dd973c91f87a6ac09dc3cde2a9f0e6a8d94fe96a16fbeSafety & 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.
Don't install it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.