Is dawn-mcpvp-installer.exe safe?
Signed installer with low-trust detection, process-injection signals, and no tier-1 consensus.
One low-trust engine flagged the file; sandbox observed LSASS access and direct-IP traffic. No tier-1 detections or known malicious children, but the signer has no prior history.
070798e224b8e025f1…8f9cc87d6330a3Recommended 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.
One low-trust engine flagged the file; sandbox observed LSASS access and direct-IP traffic. No tier-1 detections or known malicious children, but the signer has no prior history.
The single low-trust detection and absence of tier-1 consensus point away from a clear malicious verdict. However, the observed MITRE techniques (T1055, T1134) and LSASS access are not typical for a benign installer. The imphash matches are framework collisions rather than strong similarity. The lack of signer history and incomplete host-reputation data leave the file in mixed-signals territory.
What We Detected
75 engines scanned the file; only VBA32 returned a malicious label (Trojan.Win32.Generic). No tier-1 engine flagged it. The binary is signed by InPvP Inc with a verified certificate, but the signer has no recorded history in our database.
Threat Behavior
Sandbox execution recorded four offensive MITRE techniques: T1055 (Process Injection), T1059.001 (PowerShell), T1134 (Access Token Manipulation), and T1560 (Data Encrypted). LSASS memory access and direct-IP connections to 172.66.167.87 and 104.20.19.95 were observed. Ten dropped children were inspected; none carried malicious verdicts.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file is not from a trusted source, avoid execution until additional reputation data or a clean signer history becomes available.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation cross-check available for the observed IPs 172.66.167.87 and 104.20.19.95
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Signed with verified certificate
- No tier-1 malicious detections
- No malicious dropped children
- Low-trust engine detection present
- Sandbox observed LSASS access
- Direct-IP network traffic without domain resolution
- Signer has no prior sample history
Treat as suspicious; do not run without further verification or updated reputation data.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 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
- 38MITRE ATT&CK techniques
- 14spawned processes
- 3network contacts
- 34filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
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: 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
dawn-mcpvp-installer.exe
070798e224b8e025f19c6839c2011e522692b813a045fed6848f9cc87d6330a3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\dawn-installer.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -File "C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\Resolve-DawnPartnerOffer.ps1" -OffersJson "C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\installer-offers.json" -OfferId "medal" -PercentFlagName "deployments.installer_offer_medal.percent"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsbC12E.tmp
C:\Users\<USER>\AppData\Local\Temp\nsbC12E.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.66.167.87
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
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.
- 172.66.167.87
- 8.8.8.8
- 104.20.19.95
- C:\Users\<USER>\AppData\Local\Temp\nsbC12E.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\Resolve-DawnPartnerOffer.ps1
- C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\NScurl.dll
- C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\installer-offers.json
- C:\Users\<USER>\AppData\Local\Temp\nss8CC0.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsn8CF1.tmp
- C:\Users\<USER>\AppData\Local\Temp\s0n1f1bu.kqg.ps1
- C:\Users\<USER>\AppData\Local\Temp\ndzeqter.be3.psm1
- C:\Users\user\AppData\Local\Temp\nsl5B39.tmp
- Global\OneSettingQueryMutex+compat+encapsulation
- Local\!BrowserEmulation!SharedMemory!Mutex
- Local\ZonesCacheCounterMutex
- Local\ZonesLockedCacheCounterMutex
- IsoScope_850_IE_EarlyTabStart_0x310_Mutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- f9a3c631a75bb7f16043…da4157Never scannednever seen before
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- 63283d303cfdaf5fd503…48c4a2Never scannednever seen before
- 18dd38cb321f7f45c7d4…909f18Never scannednever seen before
- 3a101fa91d4e8831dfb7…9b473cNever scannednever seen before
- 5609d4fcf3eae0ac800f…d258deNever scannednever seen before
- 9639b46057f544e22f3b…76fed1Never scannednever seen before
- 4904908a060ebf730d43…ffec3bNever scannednever seen before
- be7a52d6d1b2e5e2c7a9…01365bNever scannednever seen before
- 996645d7f16a6294babb…dc51a5Never 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
- 1 / 75engines flagged
- 1,391sources 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
1 of 75 antivirus engines flagged the file, including VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from InPvP Inc.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: dawn-mcpvp-installer.exe — 070798e224b8e025f19c6839c2011e522692b813a045fed6848f9cc87d6330a3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\dawn-installer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -File "C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\Resolve-DawnPartnerOffer.ps1" -OffersJson "C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\installer-offers.json" -OfferId "medal" -PercentFlagName "deployments.installer_offer_medal.percent"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsbC12E.tmp — C:\Users\<USER>\AppData\Local\Temp\nsbC12E.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsqC13E.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 172.66.167.87 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 8.8.8.8 — 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\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.
Evidence172.66.167.87 · 104.20.19.95
1 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- dawn-mcpvp-installer.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: InPvP Inc
- Size
- 3.3 MB
- Last analyzed
- Sep 5, 2026, 2:35 PM UTC
070798e224b8e025f19c6839c2011e522692b813a045fed6848f9cc87d6330a3Safety & 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 dawn-mcpvp-installer.exe safe, or is it malware?
What is dawn-mcpvp-installer.exe?
How many antivirus engines detected dawn-mcpvp-installer.exe?
What should I do if I already installed dawn-mcpvp-installer.exe?
How do I remove dawn-mcpvp-installer.exe?
Is dawn-mcpvp-installer.exe digitally signed?
What is the SHA-256 hash of dawn-mcpvp-installer.exe?
How up to date is this analysis of dawn-mcpvp-installer.exe?
Community
Member reviews and reports for this exact file hash.