Is dxconfig.exe safe?
Unsigned 64 KB executable with one sandbox run, two low-trust detections, and direct-IP traffic.
Two engines flagged the file while 71 did not; no tier-1 consensus exists. The binary is unsigned, performed direct-IP connections, and created persistence-related artifacts, yet sandbox verdicts stayed clean.
62fbed56608e42ed7d…96399e8170e2cfRecommended 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 engines flagged the file while 71 did not; no tier-1 consensus exists. The binary is unsigned, performed direct-IP connections, and created persistence-related artifacts, yet sandbox verdicts stayed clean.
The low engine count and absence of tier-1 detections keep the sample out of the malicious band, but the unsigned status, T1543.003 technique, and direct-no complete contacted-host reputation result was available classification. Medium prevalence over nine years and zero external-intel hits add uncertainty rather than reassurance. The combination of mixed signals lands the file in the suspicious range.
What We Detected
Two of 78 engines (APEX low_trust, CrowdStrike tier2) returned malicious labels; 18 tier-1 engines stayed silent. The file is unsigned and contains no packer evidence.
Threat Behavior
One sandbox recorded MITRE technique T1543.003 and eight direct-IP connections. No malicious child files were dropped and no sandbox verdict labeled the run malicious.
What To Do Now
Run the sample only in an isolated environment, monitor for persistence changes, and keep endpoint protection enabled. Re-scan after additional sandbox coverage or external-intel updates.
Where this verdict could be wrong1 caveat
- communityComments mention low falcon-threatscores (39/100 and 20/100) from Hybrid Analysis
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 tier-1 detections
- no external-intel hits
- medium long-term prevalence
- unsigned executable
- T1543.003 technique observed
- direct-IP network traffic without domain resolution
Treat as untrusted; do not execute on production systems until further sandbox or reputation data becomes available.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 78 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial10 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 7MITRE ATT&CK techniques
- 4spawned processes
- 10network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a system service, which can keep code running.
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.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
dxconfig.exe
62fbed56608e42ed7da204526916edb91622e6e1c9fd04a2c396399e8170e2cf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\62fbed56608e42ed7da204526916edb91622e6e1c9fd04a2c396399e8170e2cf.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
servicereg.log
C:\servicereg.log
04Isolated runtime analysis - Written fileObserved
servicestart.log
C:\servicestart.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.216.147.64
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.133.109
- 23.216.147.64
- 20.99.184.37
- 192.229.211.108
- a83f:8110:2e00:3100:3900:3000:3000:3300
- 192.168.0.67
- 23.216.81.152
- 192.168.0.58
- 104.71.214.69
- <MACHINE_DNS_SERVER>
- C:\servicereg.log
- C:\servicestart.log
- \Device\ConDrv\\Connect
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF906.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF917.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF947.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF5C9.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF78F.tmp.csv
- \Sessions\1\BaseNamedObjects\M3_DATA_RECOVERY_MUTEX_20140716
- \Sessions\1\BaseNamedObjects\DATA_RECOVERY_HUNTER_MUTEX_20111001
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 596ccc911c1772735aac…43fa7bNever scannednever seen before
- b393319853ea3fe8f4bc…1d717eNever 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.
- 1rule hit recorded
- 2 / 78engines flagged
- 15sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 78 antivirus engines flagged the file, including APEX and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 17 times from 15 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: dxconfig.exe — 62fbed56608e42ed7da204526916edb91622e6e1c9fd04a2c396399e8170e2cf
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\AppData\Local\Temp\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — %SAMPLEPATH%\62fbed56608e42ed7da204526916edb91622e6e1c9fd04a2c396399e8170e2cf.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: servicereg.log — C:\servicereg.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: servicestart.log — C:\servicestart.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.147.64 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence20.99.133.109 · 23.216.147.64 · 20.99.184.37
2 of 78 engines flagged this file
View all 78 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
- dxconfig.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 63.0 KB
- Last analyzed
- Aug 6, 2026, 3:45 PM UTC
62fbed56608e42ed7da204526916edb91622e6e1c9fd04a2c396399e8170e2cfSafety & 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 dxconfig.exe safe, or is it malware?
What is dxconfig.exe?
How many antivirus engines detected dxconfig.exe?
I already downloaded and ran dxconfig.exe — what should I do?
How do I remove dxconfig.exe?
What is the SHA-256 hash of dxconfig.exe?
How up to date is this analysis of dxconfig.exe?
Community
Member reviews and reports for this exact file hash.