Is YTDPsetup_v1.7.0.msi safe?
Unsigned 14-day-old MSI shows sandbox evidence of process injection and LSASS access despite zero AV detections.
No antivirus engine flagged the file, yet the sandbox recorded T1055 process injection and LSASS memory access. The package is unsigned and only 14 days old, leaving the observed behaviour unexplained by a known benign pattern.
101b3ad2a0c7462724…f35a65fa09fc7eRecommended 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.
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.
No antivirus engine flagged the file, yet the sandbox recorded T1055 process injection and LSASS memory access. The package is unsigned and only 14 days old, leaving the observed behaviour unexplained by a known benign pattern.
Zero detections across 75 engines and medium prevalence reduce the likelihood of commodity malware. However, the single sandbox run captured MITRE T1055 and LSASS-targeted activity that legitimate installers rarely perform. Because the file is unsigned and contacted an IP address without no complete contacted-host reputation result was available and malicious. contactedHosts is null, so no external host reputation can resolve the ambiguity.
What We Detected
75 antivirus engines returned zero malicious or suspicious verdicts. The MSI is unsigned and first appeared 14 days ago with medium submission volume.
Threat Behavior
One sandbox execution recorded MITRE T1055 (process injection) and activity touching LSASS, flagged by internal heuristics as possible credential-dumping behaviour. A single external IP was contacted; no domains were resolved and host reputation data is unavailable.
What To Do Now
Do not run the installer on production systems until the observed LSASS access is explained by the software vendor. Keep Windows Defender and other endpoint protection enabled; consider executing the package in an isolated VM with network monitoring if installation is required.
Where this verdict could be wrong1 caveat
- Sandbox observed T1055 process injection and LSASS access (MalwareTips.Synth.ProcessInjection, MalwareTips.Synth.CredentialDumper) — legitimate installers rarely exhibit these patterns.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- Medium prevalence (56 submitters)
- Unsigned Windows Installer
- Sandbox observed T1055 process injection
- Sandbox observed LSASS memory access
- Direct IP contact without domain context
Treat the package as untrusted until the vendor provides a signed build or independent confirmation that the observed LSASS access is a false positive from its USB-checking routine.
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.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 5MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 8filesystem & 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: Used removable-media replication behaviour that can spread files between devices.
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.
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
YTDPsetup_v1.7.0.msi
101b3ad2a0c7462724d55663a398f9d4f287c41579eb4d8650f35a65fa09fc7e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\YTDPsetup_v1.7.0.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
MSIffe35.tmp
C:\MSIffe35.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.
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:\MSIffe35.tmp
- C:\Windows\Fonts
- C:\Windows\system32\catroot
- C:\Windows\system32\catroot2
- C:\MSIffe35.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:7072: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.
- 3rule hits recorded
- 0 / 75engines flagged
- 56sources 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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 58 times from 56 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: YTDPsetup_v1.7.0.msi — 101b3ad2a0c7462724d55663a398f9d4f287c41579eb4d8650f35a65fa09fc7e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\YTDPsetup_v1.7.0.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: MSIffe35.tmp — C:\MSIffe35.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — 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\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
- YTDPsetup_v1.7.0.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 12.4 MB
- Last analyzed
- Sep 2, 2026, 5:50 PM UTC
101b3ad2a0c7462724d55663a398f9d4f287c41579eb4d8650f35a65fa09fc7eSafety & 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 install 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. Download a fresh installer 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 YTDPsetup_v1.7.0.msi safe, or is it malware?
What is YTDPsetup_v1.7.0.msi?
How many antivirus engines detected YTDPsetup_v1.7.0.msi?
What should I do if I already installed YTDPsetup_v1.7.0.msi?
How do I remove YTDPsetup_v1.7.0.msi?
What is the SHA-256 hash of YTDPsetup_v1.7.0.msi?
How up to date is this analysis of YTDPsetup_v1.7.0.msi?
Community
Member reviews and reports for this exact file hash.