Is A_New_Dawn.exe safe?
Unsigned executable exhibiting process injection and direct-IP C2 with no AV detections.
No engines flagged the sample, yet sandbox behaviour shows T1055 process injection, T1562.001 defence evasion, and four direct-IP connections without DNS resolution. The single similar-hash precedent was also rated suspicious on the same behavioural pattern.
f36c297f6ea366fa01…1fc20c55bfbdfcRecommended 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.
No engines flagged the sample, yet sandbox behaviour shows T1055 process injection, T1562.001 defence evasion, and four direct-IP connections without DNS resolution. The single similar-hash precedent was also rated suspicious on the same behavioural pattern.
Zero malicious detections across 71 engines rules out widespread known malware, but the behavioural evidence is inconsistent with typical benign software. The file performed process injection and contacted raw IPs instead of using DNS, both flagged by high-severity heuristics. Lack of code signing and only one prior imphash match previously scored suspicious further support caution. Medium prevalence indicates the binary is not brand new, yet the combination of signals places it in the mixed-evidence zone rather than clean or malicious.
What We Detected
71 of 75 engines returned clean results; none assigned a malicious label. The executable is unsigned and carries no publisher history. Sandbox execution recorded MITRE techniques T1055 (process injection) and T1562.001 (impair defences) plus four direct-IP connections with zero DNS lookups.
Threat Behavior
Process-injection activity and direct-IP C2 are techniques rarely seen in legitimate commodity software. The file wrote multiple WerFault crash-dump artefacts and created several WER-related mutexes, consistent with attempts to blend into system processes. No dropped children were flagged malicious and no external-intel sources returned hits.
What To Do Now
Do not execute the file on production systems. If the binary is required, run it only in an isolated analysis environment and monitor for further C2 or persistence attempts. Consider requesting the original source or a signed build from the developer.
Where this verdict could be wrong2 caveats
- Zero engine detections and medium prevalence could indicate a legitimate but uncommon tool; however the combination of process-injection MITRE techniques and direct-IP C2 without DNS outweighs that possibility.
- Unsigned status leaves open the chance of a stolen or self-signed binary, but no brandMismatch or adversarial filename signals are present.
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 engine detections across 71 reporters
- Medium prevalence (28 submitters)
- No malicious dropped children or sandbox verdicts
- Process injection (T1055) observed in sandbox
- Direct-IP C2 without DNS resolution
- Unsigned executable with no signer history
- Prior imphash match previously rated suspicious
Treat as suspicious pending further analysis; isolate and monitor if execution is unavoidable.
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
Partial5 runtime contacts were 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
- 14MITRE ATT&CK techniques
- 9spawned processes
- 5network contacts
- 39filesystem & 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: 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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Communicates over the network in a non-standard way.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
A_New_Dawn.exe
f36c297f6ea366fa015100406ca59f583df299e240a6408d901fc20c55bfbdfc
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 4136 -s 464
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
2fe685bf-d778-44c3-8704-a7312aebe86d
C:\ProgramData\Microsoft\Windows\WER\Temp\2fe685bf-d778-44c3-8704-a7312aebe86d
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.42
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.46.228.5
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.
- 192.168.0.42
- 23.46.228.5
- 20.99.133.109
- 184.27.218.92
- 20.189.173.22
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\2fe685bf-d778-44c3-8704-a7312aebe86d
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\bcc5692d-18f0-495b-9dd4-4b0fc087dcdb
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC301.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA84.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC89.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC301.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA84.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess4136
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\41426f46-4293-4d7f-ad96-2b12b1358b72
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3676
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex5080
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 332557f35c6c5091fcdd…73ff67Never scannednever seen before
- a2b9949ade90c5d5d49e…9e2d46Never scannednever seen before
- e55844c2c5de03edfaea…bbdf98Never scannednever seen before
- 694e8c6934dfc3ab175c…499f62Never scannednever seen before
- caccf87e4b812302fb0c…0c61b1Never scannednever seen before
- 41fc90a1e37020115731…e9ab9fNever 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 / 75engines flagged
- 28sources 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 29 times from 28 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: A_New_Dawn.exe — f36c297f6ea366fa015100406ca59f583df299e240a6408d901fc20c55bfbdfc
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 4136 -s 464
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 2fe685bf-d778-44c3-8704-a7312aebe86d — C:\ProgramData\Microsoft\Windows\WER\Temp\2fe685bf-d778-44c3-8704-a7312aebe86d
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.42 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.46.228.5 — 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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Users\<USER>\Desktop\program.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.
Evidence23.46.228.5 · 20.99.133.109 · 184.27.218.92
0 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
- A_New_Dawn.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 301.0 KB
- Last analyzed
- Jul 5, 2026, 3:03 AM UTC
f36c297f6ea366fa015100406ca59f583df299e240a6408d901fc20c55bfbdfcSafety & 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 A_New_Dawn.exe safe, or is it malware?
What is A_New_Dawn.exe?
How many antivirus engines detected A_New_Dawn.exe?
What should I do if I already ran A_New_Dawn.exe?
How do I remove A_New_Dawn.exe?
What is the SHA-256 hash of A_New_Dawn.exe?
How up to date is this analysis of A_New_Dawn.exe?
Community
Member reviews and reports for this exact file hash.