Is SlaythePrincess.exe safe?
No antivirus engine detected malware, and years of broad circulation plus a non-malicious sandbox result strongly outweigh the isolated T1055 behavioral mapping.
The file received no detections from 75 antivirus engines, including all 17 tier-1 engines, despite broad circulation since 2022. One sandbox mapped activity to process injection technique T1055, but it produced no malicious verdict, contacted only fully checked Microsoft domains, and yielded no confirmed malicious child.
8a8cf2c2eaa50070fd…0ab84c695d9c19Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
The file received no detections from 75 antivirus engines, including all 17 tier-1 engines, despite broad circulation since 2022. One sandbox mapped activity to process injection technique T1055, but it produced no malicious verdict, contacted only fully checked Microsoft domains, and yielded no confirmed malicious child.
No engine among 75 identified malware or suspicious content, and all 17 tier-1 products were silent. The sample has circulated through 1,399 sources and 1,626 submissions since July 2022, making an undetected long-running threat less likely. One completed sandbox run did not produce a malicious verdict, and its two observed domains were fully covered by the host-reputation check without malicious or suspicious findings. The principal concern is a T1055 process-injection mapping, but the underlying evidence does not establish a specific injection method or hostile purpose. The lack of a digital signature and unresolved child-file verdicts reduce certainty, yet they do not outweigh the strong antivirus, prevalence, and runtime evidence.
What We Detected
None of 75 antivirus engines flagged the executable, including all 17 tier-1 engines. The file has also been submitted 1,626 times by 1,399 sources since July 2022, providing substantial historical exposure without a named malware family or detection.
Threat Behavior
One completed sandbox run did not issue a malicious verdict and recorded no persistence indicators. A heuristic mapped activity to MITRE T1055, which can represent process injection, but the saved evidence does not prove the exact technique or malicious intent. Both observed domains—www.microsoft.com and res.public.onecdn.static.microsoft—were covered by the host-reputation check and had no malicious or suspicious cache verdict. Two dropped files were inspected without a confirmed malicious result, though their individual verdicts remain unknown.
What To Do Now
Use a copy obtained from the game's official distribution channel and retain endpoint protection during installation and execution. Because the executable is unsigned, compare its SHA-256 hash with a trusted publisher or storefront listing when available.
Where this verdict could be wrong3 caveats
- The executable is unsigned: signing.applicable=true and signing.signed=false, so publisher identity cannot be authenticated.
- behaviour.offensiveTechniques contains T1055 (Process Injection), although the saved mapping does not establish the exact method or malicious intent.
- droppedChildren inspected two hashes, but both child verdicts are unknown rather than affirmatively clean.
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/75 antivirus engines detected malware or suspicious content
- All 17 tier-1 engines reported no detection
- 1,399 sources and 1,626 submissions since July 2022
- One sandbox completed without a malicious verdict
- Both observed domains received complete host-reputation coverage without malicious or suspicious findings
- Unsigned Win32 executable with no authenticated publisher
- Runtime evidence mapped to MITRE T1055 process injection
- Two dropped child files have unknown individual verdicts
- Detect-debug-environment tag indicates anti-analysis awareness
Prefer the official storefront or developer download and verify SHA-256 8a8cf2c2eaa50070fde1b614af9482fc763639a8e8cc965a300ab84c695d9c19 when a trusted hash is available. Keep endpoint protection enabled.
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
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
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
- 9MITRE ATT&CK techniques
- 12spawned processes
- 22network contacts
- 34filesystem & mutex artifacts
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.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- 64.233.181.94
- 23.55.168.64
- 192.168.0.58
- 52.185.73.156
- 23.216.81.152
- 20.99.186.246
- 23.192.210.9
- 192.168.0.61
- 23.216.147.61
- 52.154.209.174
- HKU\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\SystemCertificates\Root\Certificates\0174E68C97DDF1E0EEEA415EA336A163D2B61AFD\Blob
- HKU\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\SystemCertificates\Root\Certificates\0174E68C97DDF1E0EEEA415EA336A163D2B61AFD\Blob
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation
- \REGISTRY\A\{61055053-0079-4c47-81a4-33388521a29c}\Root\InventoryApplicationFile\WritePermissionsCheck
- \REGISTRY\A\{61055053-0079-4c47-81a4-33388521a29c}\Root\InventoryApplicationFile\executable.exe|7c5e06e72bd459d4\ProgramId
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\63c85667-87b8-4ded-8405-b64f42b5ee84
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\719336b1-a085-4f02-b122-b97ec1ea6330
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3454.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CF0.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5339.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3454.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CF0.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess5848
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\02421775-beb4-4cc0-a221-3f26622c7d4c
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7448
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 8766b987434b148c1fe5…c92a0fNever scannednever seen before
- 0468bccb74c8ab52da30…86efd3Never 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
- 0 / 75engines flagged
- 1,399sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,399 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: SlaythePrincess.exe — 8a8cf2c2eaa50070fde1b614af9482fc763639a8e8cc965a300ab84c695d9c19
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 5848 -s 200
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 63c85667-87b8-4ded-8405-b64f42b5ee84 — C:\ProgramData\Microsoft\Windows\WER\Temp\63c85667-87b8-4ded-8405-b64f42b5ee84
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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"
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- SlaythePrincess.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 120.0 KB
- Last analyzed
- Oct 5, 2026, 11:44 AM UTC
8a8cf2c2eaa50070fde1b614af9482fc763639a8e8cc965a300ab84c695d9c19Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is SlaythePrincess.exe safe?
What is SlaythePrincess.exe?
How many antivirus engines detected SlaythePrincess.exe?
What is the SHA-256 hash of SlaythePrincess.exe?
Is it safe to run SlaythePrincess.exe?
How up to date is this analysis of SlaythePrincess.exe?
Community
Member reviews and reports for this exact file hash.