Is jjsploit.exe safe?
Unsigned 18 MB executable flagged by two engines as game-hack tool with process-injection and LSASS-access behaviour.
Two of 75 engines flag the file as RiskWare.GameHack; sandbox shows T1055 process injection, T1485 data destruction, and LSASS access. The file is unsigned and has no tier-1 consensus, placing it in mixed-signal territory.
f26df72e97bdfd28ed…77c83a27649d69Recommended 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.
Two of 75 engines flag the file as RiskWare.GameHack; sandbox shows T1055 process injection, T1485 data destruction, and LSASS access. The file is unsigned and has no tier-1 consensus, placing it in mixed-signal territory.
The sample triggers three offensive MITRE techniques and direct-IP contact, yet only two engines detect it and none are tier-1. Absence of code signing and lack of historical RAG matches keep the file out of the safe category. Medium prevalence and no dropped malicious children prevent an outright malicious call. The combination of offensive runtime signals and low engine consensus yields a suspicious verdict.
What We Detected
Two engines (Malwarebytes tier-2, Trapmine low-trust) label the file RiskWare.GameHack. Sandbox execution recorded process injection (T1055), defense evasion (T1562.001), and data destruction (T1485) plus LSASS memory access. The binary is unsigned and contacts one external IP directly.
Threat Behavior
Observed actions match common game-hack tooling patterns: injection into legitimate processes, tampering with security mechanisms, and credential-store probing. No tier-1 engine consensus or known-malicious children were found.
What To Do Now
Do not execute on production systems. Keep endpoint protection enabled. If the file is required for research, run it only in an isolated virtual machine with network monitoring.
Where this verdict could be wrong2 caveats
- engines.tier1Malicious=0 and 17 tier-1 engines reported clean — limited high-trust consensus.
- droppedChildren.hasMaliciousChild=false and 10 children inspected with no malicious verdicts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 malicious detections
- No malicious dropped children
- Medium prevalence with multiple submitters
- Unsigned executable
- Process injection (T1055)
- LSASS access observed
- Direct-IP contact without domain
Treat as potentially unwanted game-hack software; avoid execution outside controlled environments and retain active antivirus protection.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 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
- 17MITRE ATT&CK techniques
- 15spawned processes
- 1network 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: Used an input-capture technique that can record credentials or keystrokes.
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: Communicated over a common application protocol; malware can use this for command-and-control.
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.exe
f26df72e97bdfd28ed22e96b9592029aa8837429fddb053c2f77c83a27649d69
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\jjsploit.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=jjsploit.exe --webview-exe-version=8.20.8 --user-data-dir="C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=2768.68.1424909882649286491
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\settings.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.29.11
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.
- 150.171.29.11
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\BrowserMetrics\BrowserMetrics-6A965F69-EEC.pma
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\lockfile
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Variations
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\f56f74b1-bcb2-46da-8ea5-0da94418153f.tmp
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Default\Code Cache\wasm\index-dir\the-real-index
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Default\Code Cache\js\index-dir\temp-index
- C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Default\Sync Data\LevelDB\000001.dbtmp
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- 9c8d3b65aca41fc9fd58…94c213Never scannednever seen before
- 007373123ea557e2be80…d8083fNever scannednever seen before
- f1333d617b63d7037dc2…2db35bNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- fb2219752b8b3bcdee4b…a7aedbNever scannednever seen before
- 090eb0b6009b6c77d0e3…6cf6a4Never 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.
- 3rule hits recorded
- 2 / 75engines flagged
- 7sources 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 75 antivirus engines flagged the file, including Malwarebytes and Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 10 times from 7 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: jjsploit.exe — f26df72e97bdfd28ed22e96b9592029aa8837429fddb053c2f77c83a27649d69
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\jjsploit.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=jjsploit.exe --webview-exe-version=8.20.8 --user-data-dir="C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=2768.68.1424909882649286491
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Local\net.wearedevs.jjsploit\EBWebView\Crashpad\settings.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.29.11 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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.
Evidence150.171.29.11
2 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- jjsploit.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 17.3 MB
- Last analyzed
- Aug 31, 2026, 11:15 PM UTC
f26df72e97bdfd28ed22e96b9592029aa8837429fddb053c2f77c83a27649d69Safety & 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 jjsploit.exe safe, or is it malware?
What is jjsploit.exe?
How many antivirus engines detected jjsploit.exe?
I already downloaded and ran jjsploit.exe — what should I do?
How do I remove jjsploit.exe?
What kind of malware is jjsploit.exe?
What is the SHA-256 hash of jjsploit.exe?
How up to date is this analysis of jjsploit.exe?
Community
Member reviews and reports for this exact file hash.