Is Darmoshark Keyboard Setup v2.2.exe safe?
No antivirus engine detected this installer, but LSASS-targeting activity, possible process injection, and unresolved direct-IP connections warrant caution before execution.
All 76 antivirus engines were silent, including 18 tier-1 products, and no malicious child or researcher-rule match was found. However, one sandbox recorded possible process injection, LSASS-targeting activity, and eight direct-IP contacts whose reputations were not checked, leaving a meaningful unresolved risk.
7de0c219c1b7b22abe…f9f4069342ea1eRecommended 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.
All 76 antivirus engines were silent, including 18 tier-1 products, and no malicious child or researcher-rule match was found. However, one sandbox recorded possible process injection, LSASS-targeting activity, and eight direct-IP contacts whose reputations were not checked, leaving a meaningful unresolved risk.
The strongest reassuring evidence is that 0 of 76 engines detected the sample, with all 18 reporting tier-1 engines silent. No malicious sandbox verdict, known malicious child, external intelligence hit, or named malware family supports a malware attribution. Against that, the completed runtime observation mapped activity to T1055 and recorded access involving LSASS, both of which deserve scrutiny in an unsigned keyboard installer. It also recorded eight direct-IP contacts, but no complete host-reputation result is available because the contacted-host cross-check was not saved. These conflicting signals support caution rather than a definitive malware finding.
What We Detected
None of 76 antivirus engines flagged the installer, including 18 tier-1 engines. External intelligence produced no MalwareBazaar, YARAify, or CIRCL hit, and no engine supplied a malware-family label.
Threat Behavior
One sandbox run recorded possible process injection mapped to T1055 and activity targeting LSASS, alongside several other offensive-technique mappings. It also observed eight direct-IP connections. Their reputation could not be established because a complete contacted-host cross-check is unavailable. Ten dropped files were inspected without a malicious child finding, although their individual verdicts remain unknown.
What To Do Now
Do not run this copy unless its SHA-256 can be matched to a download published through Darmoshark's official release channel. Keep endpoint protection enabled, and if the installer has already run, review endpoint alerts and outbound connections involving the listed IP addresses.
Where this verdict could be wrong4 caveats
- The complete 0/76 detection result, including 18 tier-1 engines without detections, weighs strongly against a known malware family.
- behaviour.hasMaliciousSandboxVerdict=false, so the single runtime environment did not independently conclude that execution was malicious.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false provide no researcher-curated corroboration.
- The file is unsigned despite signing.applicable=true, so publisher identity cannot offset the concerning runtime indicators.
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 of 76 antivirus engines detected the file
- 18 tier-1 engines reported no detection
- No malicious sandbox verdict was recorded
- No malicious dropped child was identified
- No MalwareBazaar, YARAify, or CIRCL hit was found
- Unsigned Win32 executable despite code signing being applicable
- Possible process injection mapped to T1055
- Runtime activity targeting LSASS
- Eight direct-IP contacts with no complete reputation cross-check
- Six offensive MITRE technique mappings
- All 10 dropped-child verdicts remain unknown
Verify SHA-256 7de0c219c1b7b22abe8bf51721609a57fcd9136c239ae5916ff9f4069342ea1e against Darmoshark's official download before use. Keep endpoint protection enabled and avoid this copy if its origin cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial8 runtime contacts were 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
- 32MITRE ATT&CK techniques
- 15spawned processes
- 8network contacts
- 40filesystem & 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: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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
Darmoshark Keyboard Setup v2.2.exe
7de0c219c1b7b22abe8bf51721609a57fcd9136c239ae5916ff9f4069342ea1e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-DEA0E.tmp\file.tmp" /SL5="$40076,1934251,247808,C:\Users\<USER>\Desktop\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.tmp
C:\Users\<USER>\AppData\Local\Temp\is-DEA0E.tmp\file.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-FE4J8.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.184.37
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.229.211.108
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 20.99.184.37
- 192.229.211.108
- 20.99.133.109
- a83f:8110:0:0:0:4000:0:0
- a83f:8110:0:0:4d8c:21:0:0
- 104.98.118.177
- 23.196.145.221
- 20.69.140.28
- C:\Users\<USER>\AppData\Local\Temp\is-DEA0E.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-FE4J8.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-FE4J8.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-FE4J8.tmp\InitSetup.dll
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\unins000.dat
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\is-ARR4N.tmp
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\Cartoon\is-S9GM8.tmp
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\Cartoon\is-VTSH4.tmp
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\ET\1\is-7V07P.tmp
- C:\Program Files (x86)\Darmoshark Gaming Keyboard\ET\1\is-Q55AC.tmp
- cversions.3.m
- Darmoshark Gaming Keyboard
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- b6e6c37a4e0caf75e7ca…1c3f78Never scannednever seen before
- f11834c8c1e25238de41…89bb8bNever scannednever seen before
- 5954b69d6ed0ecc51099…51cda2Never scannednever seen before
- d2874553e324b2781d50…ea1512Never scannednever seen before
- 24045ec3fe62eff485e2…320138Never scannednever seen before
- 2bcf22070c224a20fd95…d57568Never scannednever seen before
- d272ef72d0d8d8eaa064…1d25d9Never scannednever seen before
- 6959d3ee60f486d22d62…c2f17dNever scannednever seen before
- bc112c7b85466f7852fe…7d4b60Never scannednever seen before
- 8f38d02f61a021ab4c6c…cf1e6eNever 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
- 0 / 76engines flagged
- 38sources 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 76 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 40 times from 38 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Darmoshark Keyboard Setup v2.2.exe — 7de0c219c1b7b22abe8bf51721609a57fcd9136c239ae5916ff9f4069342ea1e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-DEA0E.tmp\file.tmp" /SL5="$40076,1934251,247808,C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-DEA0E.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-FE4J8.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.229.211.108 — 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\Explorer.EXESandbox 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.
Evidence20.99.184.37 · 192.229.211.108 · 20.99.133.109
0 of 76 engines flagged this file
View all 76 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
- Darmoshark Keyboard Setup v2.2.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.2 MB
- Last analyzed
- Sep 15, 2026, 12:25 PM UTC
7de0c219c1b7b22abe8bf51721609a57fcd9136c239ae5916ff9f4069342ea1eSafety & 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 Darmoshark Keyboard Setup v2.2.exe safe, or is it malware?
What is Darmoshark Keyboard Setup v2.2.exe?
How many antivirus engines detected Darmoshark Keyboard Setup v2.2.exe?
I already downloaded and installed Darmoshark Keyboard Setup v2.2.exe — what should I do?
How do I remove Darmoshark Keyboard Setup v2.2.exe?
What is the SHA-256 hash of Darmoshark Keyboard Setup v2.2.exe?
How up to date is this analysis of Darmoshark Keyboard Setup v2.2.exe?
Community
Member reviews and reports for this exact file hash.