Is DualSenseY.exe safe?
No antivirus engine detected malware, but observed process-injection mapping and unresolved direct-IP traffic warrant caution until the executable's source is verified.
None of 74 engines flagged the executable, and no malicious family, child, or researcher rule corroborated it. However, one sandbox run mapped activity to process injection and nonstandard-protocol communication, while an external IP contact lacked a completed reputation check, so the file should not be trusted solely on the scan result.
b103839d958e665836…50cb8d769de15dRecommended 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.
None of 74 engines flagged the executable, and no malicious family, child, or researcher rule corroborated it. However, one sandbox run mapped activity to process injection and nonstandard-protocol communication, while an external IP contact lacked a completed reputation check, so the file should not be trusted solely on the scan result.
The static scan is strongly reassuring: 0 of 74 engines reported a detection, including no tier-1 alerts. One completed sandbox observation nevertheless mapped activity to T1055 and T1571 and recorded a direct connection to 65.21.225.215. No complete host-reputation result is available for that IP, so its role cannot be resolved from this evidence. The executable is unsigned, and no established publisher history supports its identity. No malicious sandbox verdict, confirmed malicious child, external-intelligence hit, packing indicator, or family consensus corroborates the concerning behavior, leaving mixed rather than conclusive evidence.
What We Detected
None of 74 antivirus engines flagged the executable, and 16 tier-1 engines reported no detection. No malware family consensus, external researcher-rule match, known-malware database hit, or suspicious packing pattern was present.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055 (Process Injection) and T1571 (Non-Standard Port), and it recorded a connection to 65.21.225.215. These are meaningful risk indicators, but the sandbox did not issue a malicious verdict. The contacted-host reputation check was not completed or saved, so the external no complete contacted-host reputation result was available. One dropped child was inspected but remains unclassified, with no confirmed malicious child.
What To Do Now
Verify the file against the official project or vendor release and compare its SHA-256 hash before running it. Keep endpoint protection enabled; if the source or hash cannot be authenticated, isolate or remove the file rather than granting elevated privileges.
Where this verdict could be wrong3 caveats
- The complete 0/74 detection result, including silence from tier-1 engines such as BitDefender, Kaspersky, ESET-NOD32, and Avast, weighs strongly against known malware.
- behaviour.hasMaliciousSandboxVerdict=false, but this does not erase the observed T1055 and direct-IP activity.
- The sole dropped child b88d66f60f54b72b8a707132389b7ee6b78a979b4a1b5d54314d349e735c92fe remains unknown rather than confirmed benign.
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/74 antivirus engines reported malicious or suspicious results.
- engines.tier1Malicious=0, with 16 tier-1 engines reporting no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- No YARAify, CIRCL, or MalwareBazaar hit was present.
- Sandbox evidence mapped activity to MITRE T1055 process injection.
- MITRE T1571 and direct-IP contact with 65.21.225.215 were observed.
- No complete reputation cross-check is available for the contacted IP.
- The Win32 executable is unsigned and has no signer history.
- The dropped child remains unclassified.
Run the file only if its SHA-256 hash can be matched to an official release from a trusted source. Keep endpoint protection enabled and avoid granting administrator privileges while the direct-IP behavior remains unresolved.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 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
- 12MITRE ATT&CK techniques
- 2spawned 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 an input-capture technique that can record credentials or keystrokes.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Moderate concern: Reaches its server over an unusual network port.
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
DualSenseY.exe
b103839d958e665836171c695fbdb3662317df9407426cc1da50cb8d769de15d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\software.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\Connect
04Isolated runtime analysis - Written fileObserved
Config.json
C:\Users\<USER>\Documents\DSY\Config.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
65.21.225.215
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.
- 65.21.225.215
- \Device\ConDrv\Connect
- C:\Users\<USER>\Documents\DSY\Config.json
- C:\Users\user\Desktop\crash_2026-06-16_20-50-34.dmp
- C:\Users\user\Documents
- C:\Users\user\Documents\DSY
- C:\Users\<USER>\Desktop\update.zip
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- b88d66f60f54b72b8a70…5c92feNever 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.
- 2rule hits recorded
- 0 / 74engines flagged
- 39sources 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 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 41 times from 39 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: DualSenseY.exe — b103839d958e665836171c695fbdb3662317df9407426cc1da50cb8d769de15d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Config.json — C:\Users\<USER>\Documents\DSY\Config.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 65.21.225.215 — 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.
Evidence"C:\Users\<USER>\Desktop\executable.exe"The 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.
Evidence65.21.225.215
0 of 74 engines flagged this file
View all 74 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
- DualSenseY.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 3.7 MB
- Last analyzed
- Sep 17, 2026, 5:01 PM UTC
b103839d958e665836171c695fbdb3662317df9407426cc1da50cb8d769de15dSafety & 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 DualSenseY.exe safe, or is it malware?
What is DualSenseY.exe?
How many antivirus engines detected DualSenseY.exe?
What should I do if I already ran DualSenseY.exe?
How do I remove DualSenseY.exe?
What is the SHA-256 hash of DualSenseY.exe?
How up to date is this analysis of DualSenseY.exe?
Community
Member reviews and reports for this exact file hash.