Safe
Zero engine detections on a widely submitted unsigned executable with only ambient sandbox behaviour.
e33d4483bce054f22c…f95960447dThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
The complete absence of malicious detections across tier-1, tier-2, and low-trust engines outweighs the single heuristic flag for direct-IP contact. Long-term prevalence and lack of any external-intel or RAG hits support a benign classification. Unsigned status prevents strong signer-based trust, yet the clean record across nearly two thousand submissions indicates low risk.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1ReportedClean=17 with malicious=0
prevalence.classification=common_old (663 sources)
triggeredHeuristics[0].rule=MalwareTips.Synth.DirectIpC2 (direct-IP contact)
signing.signed=false
behaviour.hasMaliciousSandboxVerdict=false
- Zero malicious detections across 75 engines
- 17 tier-1 engines reported clean
- Common-old prevalence with 663 unique sources
- No malicious sandbox verdict or known-bad hosts
- Unsigned executable
- Direct-IP network contact without DNS
Treat as low-risk based on unanimous clean engine results and long submission history; exercise normal caution with any unsigned executable.
What to do now
This file looks safe based on everything we checked.
This file is safe to use.
Good habit: only download files from the official website or an app store.
Keep your antivirus and Windows updates switched on so you stay protected.
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.
- 13.107.4.50
- 23.216.147.64
- 168.62.242.76
- 13.107.39.203
- 20.99.132.105
- a83f:8110:6e6b:2000:af3f:312f:2ba0:d201
- 20.99.133.109
- a83f:8110:0:0:678a:21:0:0
- 20.99.184.37
- 52.185.73.156
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
- C:\Users\<USER>\Desktop\output_log.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A45.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A46.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B1F.tmp.csv
- DDrawWindowListMutex
- DDrawDriverObjectListMutex
- __DDrawExclMode__
- __DDrawCheckExclMode__
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
YARA & heuristic rule matches
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 19 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence13.107.4.50 · 23.216.147.64 · 168.62.242.76
0 detections across 75 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked 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.
Forensic fingerprint
- File name
- Castle of Temptation.exe
- Size
- 16.11 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- e33d4483bce054f22cdbe6cd791ff1fd689edfcb8422b04fbe31d7f95960447d
- MD5
- 828b512a1288b476788543fa46698bc8
- SHA-1
- 8ffa43030af5d6b37e944b83d859001280c1cb7c
- PE imphash
- db5533103393574c1fe1d840e8e9ff90
- First seen (VT)
- 8/2/2021, 2:53:59 PM
- Last analysis (VT)
- 6/16/2026, 8:31:28 AM
- First scan (MalwareTips)
- 7/18/2026, 9:52:19 AM
- Last scan (MalwareTips)
- 7/18/2026, 9:52:19 AM
- Community reputation
- +1trusted
Safety FAQ
Common questions about Castle of Temptation.exe, answered from the scan data above.
- Castle of Temptation.exe appears safe. 75 of 75 antivirus engines report it clean. As a habit, only run files you downloaded from the official source, since attackers sometimes distribute trojanised copies of legitimate software under the same name.
- Castle of Temptation.exe is a Windows executable program, about 16.1 MB. Our analysis found no threat indicators for it. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- None — all 75 antivirus engines we queried report Castle of Temptation.exe as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- The SHA-256 hash of Castle of Temptation.exe is e33d4483bce054f22cdbe6cd791ff1fd689edfcb8422b04fbe31d7f95960447d, and its MD5 is 828b512a1288b476788543fa46698bc8. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- Based on this scan, yes — Castle of Temptation.exe shows no threat indicators. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it while we report it clean, that is most often a false positive, but verify the source before overriding your antivirus.
- This report reflects the scan run on July 18, 2026. Because a file's hash never changes, the identity of Castle of Temptation.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.