Is jjsploit_8.18.4_x64_en-US.msi safe?
Unsigned installer shows sandbox process-injection and LSASS access despite zero engine detections.
No antivirus engine flagged the file, yet sandbox evidence shows T1055 process injection and LSASS memory access. The package is unsigned and widely distributed, creating conflicting signals that prevent a clean classification.
ea003af9543a0300e6…581be59f9780c5Recommended 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 sandbox evidence shows T1055 process injection and LSASS memory access. The package is unsigned and widely distributed, creating conflicting signals that prevent a clean classification.
Seventy-five engines, including all tier-1 scanners, returned clean results. However, the single sandbox run recorded offensive MITRE T1055 activity and LSASS targeting, both mapped by internal heuristics. The MSI is unsigned and carries FileScan.IO researcher annotations citing keylogger and anti-debug traits. High submission volume indicates broad distribution, but the lack of signing and the observed runtime techniques keep the sample in mixed-signal territory.
What We Detected
Zero of 75 engines reported malicious content. Sandbox execution captured process-injection behaviour (T1055) and LSASS memory reads. The installer is unsigned and carries community annotations that list keylogger, anti-debug, and reconnaissance tags.
Threat Behavior
Observed actions map to credential-dumping patterns, yet no C2 traffic, dropped children, or persistence mechanisms were recorded. The file is distributed widely, suggesting either a popular legitimate tool or a commodity dropper that has so far evaded signature detection.
What To Do Now
Do not execute the installer on production systems. Keep endpoint protection enabled and consider running the file in an isolated virtual machine with network monitoring if further analysis is required.
Where this verdict could be wrong2 caveats
- Zero detections across 75 engines including 17 tier-1 engines
- prevalence.classification=common_new with 2381 submissions suggests widespread legitimate distribution
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
- High submission volume (2381) indicates wide distribution
- Unsigned Windows Installer
- Sandbox observed T1055 process injection
- LSASS memory access recorded
- Community annotations cite keylogger and anti-debug traits
Treat the installer as untrusted; run only in a controlled environment with active monitoring until signing status or additional corroboration is obtained.
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
PartialIndependent reference checks were attempted but are incomplete.
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
- 10filesystem & 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.
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
jjsploit_8.18.4_x64_en-US.msi
ea003af9543a0300e61e0e4df3ed6347fc4eb89fa79a110467581be59f9780c5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\jjsploit_8.18.4_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
MSI8c79b.tmp
C:\MSI8c79b.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:\MSI8c79b.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Windows\Fonts
- C:\MSI8c79b.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:3096: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
- 2,000sources 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 2,381 times from 2,000 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: jjsploit_8.18.4_x64_en-US.msi — ea003af9543a0300e61e0e4df3ed6347fc4eb89fa79a110467581be59f9780c5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\jjsploit_8.18.4_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: MSI8c79b.tmp — C:\MSI8c79b.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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
- jjsploit_8.18.4_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 6.0 MB
- Last analyzed
- Aug 4, 2026, 9:03 PM UTC
ea003af9543a0300e61e0e4df3ed6347fc4eb89fa79a110467581be59f9780c5Safety & 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 jjsploit_8.18.4_x64_en-US.msi safe, or is it malware?
What is jjsploit_8.18.4_x64_en-US.msi?
How many antivirus engines detected jjsploit_8.18.4_x64_en-US.msi?
What should I do if I already installed jjsploit_8.18.4_x64_en-US.msi?
How do I remove jjsploit_8.18.4_x64_en-US.msi?
What is the SHA-256 hash of jjsploit_8.18.4_x64_en-US.msi?
How up to date is this analysis of jjsploit_8.18.4_x64_en-US.msi?
Community
Member reviews and reports for this exact file hash.