MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 1 month ago

Is A Plague Tale Ultrawide.exe safe? No, we rate this exact file malicious.

The file is consistently identified as a Cheat Engine-based game hack or riskware tool: 33 of the 71 antivirus engines that checked it flagged it, including six major antivirus…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Remove it unless you use it on purpose

Keep it only if you installed it on purpose for security testing. Otherwise delete it and run a full antivirus scan.

What to do now4 steps

This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.

What to do

  1. Don't run it unless you got it on purpose for security testing on systems you own. Delete it, then empty the Recycle Bin.

  2. If you didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.

  3. Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

A Plague Tale Ultrawide.exe: Malicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

33 of 71 flagged

  • Flagged 33
  • No detection 38
  • No result 4
FileA Plague Tale Ultrawide.exe6.0 MBSHA-256 bcf34541929b…d403b5
  • Code signing Unsigned
  • Test run Completed
  • First seen 6y ago
33 of the 71 antivirus engines that checked it flag it, including Microsoft and ESET.

Chapter 02

Why we think so

5 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Thirty-three of the 71 antivirus engines that checked it detected the executable, and six major antivirus engines contributed detections. ESET-NOD32 specifically identified Cheat Engine hacking tool functionality, while GData and Ikarus also used hacking tool classifications. The corroborated hacking tool flag is decisive under the handling policy, regardless of whether the intended use is modifying a game. The executable is unsigned, and no complete reputation check is available for the observed direct-IP contacts.

Where this verdict could be wrong5 caveats
  • Major antivirus engines do not agree on one malware family; only 2 major antivirus engines converged specifically on Cheat Engine, although six major antivirus engines flagged the file overall.
  • No sandbox returned a malicious verdict, and no dropped file is known to be malicious across 6 inspected children.
  • No community YARA rule matched and the hash is not in the known-software reference database, providing no researcher-curated corroboration.
  • The file is widely seen and long established with 121 sources and 128 submissions, indicating this is not a sample.
  • PE analysis reports the absence of packed-level code entropy and the absence of packing indicators.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 14sandbox rule tags
  • 14spawned processes
  • 1network contact
  • 32filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Listed the programs running on the test computer.

  • Note: Deleted files or logs during the test run (installers often clean up after themselves).

  • Note: Talked to servers over the internet during the test run.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

  • Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Threat context

How hacking tools are used

Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.

Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 6: FileSeen in the test run

      A Plague Tale Ultrawide.exe

      bcf34541929b4cdf11e8967cbc1fc3eb5444868af1829794db75eea586d403b5

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 6: ProcessSeen in the test run

      file.exe

      "C:\Users\<USER>\Desktop\file.exe"

      Test run
    2. Evidence 3 of 6: ProcessSeen in the test run

      file.exe

      "C:\Users\<USER>\AppData\Local\Temp\cetrainers\CETCD52.tmp\file.exe" -ORIGIN:"C:\Users\<USER>\Desktop\"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 6: Written fileSeen in the test run

      CET_Archive.dat

      C:\Users\<USER>\AppData\Local\Temp\cetrainers\CETCD52.tmp\CET_Archive.dat

      Test run
    2. Evidence 5 of 6: Written fileSeen in the test run

      file.exe

      C:\Users\<USER>\AppData\Local\Temp\cetrainers\CETCD52.tmp\file.exe

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    1
    1. Evidence 6 of 6: Contacted hostSeen in the test run

      23.40.197.184

      Contacted during the test run.

      Test run

6 facts from the test run. See the full activity list.

Chapter 04

Technical details

33 of the 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 33 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 host contacted in the test run had no completed reputation check Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 33

  • ESET-NOD32 (major engine)Win32/HackTool.CheatEngine.AF potentially unsafe application
  • Fortinet (major engine)Riskware/CheatEngine
  • GData (major engine)Win32.Riskware.Hacktool.D
  • Ikarus (major engine)Riskware.Win32.Hacktool
  • Microsoft (major engine)PUA:Win32/Presenoker
  • Sophos (major engine)Generic Reputation PUA (PUA)
  • TrellixENS (major engine)GenericRXWU-YA!D50CC918E1C0
  • alibabacloudHackTool:Win/CheatEngine.A#
25 more in the full engine list

File fingerprint

Last analyzed
Sep 9, 2026, 8:28 PM UTC
SHA-256
bcf34541929b4cdf11e8967cbc1fc3eb5444868af1829794db75eea586d403b5
SHA-1
8be27d93d2f9c30c4706af78d8741baae9d888ed
MD5
d50cc918e1c0d551fe6d6a697d391273

About this file

A Plague Tale Ultrawide.exe is a Win32 EXE file of 6.0 MB.

Type and size
Win32 EXE · 6.0 MB
Signer
UnsignedNo code signature.
First seen
Jan 26, 2020On VirusTotal.
Submitted by
121 distinct sources
Packer
None detected
Entropy
7.97 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 8 questions people ask most about this file.

Is A Plague Tale Ultrawide.exe a virus?
A Plague Tale Ultrawide.exe is a hacking tool. It is flagged because it can be misused, not because it infects a device by itself. Keep it only if you use it on purpose; otherwise, delete it, then empty the Recycle Bin. 33 of the 71 antivirus engines that checked it flag it, some as Cheat Engine.
What is A Plague Tale Ultrawide.exe?
A Plague Tale Ultrawide.exe is a Windows program, about 6.0 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Jan 26, 2020.
How many antivirus engines detected A Plague Tale Ultrawide.exe?
33 of the 71 antivirus engines that checked it flag A Plague Tale Ultrawide.exe, including Microsoft and ESET. We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
What should I do if I already ran A Plague Tale Ultrawide.exe?
1) If you ran it on purpose, for testing on systems you own, remove it when you are done. 2) If you didn't download it yourself, delete it and run a full antivirus scan: something else may have brought it. 3) If it came with cracked or pirated software, treat that whole download as unsafe, scan everything it installed and change passwords you typed on the device since.
How do I remove A Plague Tale Ultrawide.exe?
To remove A Plague Tale Ultrawide.exe: 1) Delete it, then empty the Recycle Bin. 2) Run a full scan with your antivirus to check that nothing else came with it. 3) Check Settings > Apps and your startup apps for anything you don't recognise.
What kind of program is A Plague Tale Ultrawide.exe?
Antivirus engines classify A Plague Tale Ultrawide.exe as a hacking tool: a program that can switch off security software, test passwords or attack other computers. Engines attribute it to the Cheat Engine family.
What is the SHA-256 hash of A Plague Tale Ultrawide.exe?
The SHA-256 fingerprint of A Plague Tale Ultrawide.exe is bcf34541929b4cdf11e8967cbc1fc3eb5444868af1829794db75eea586d403b5, and its MD5 is d50cc918e1c0d551fe6d6a697d391273. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of A Plague Tale Ultrawide.exe?
This report reflects the scan on Sep 9, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Other files people checked with the same threat family, and recent reports with the same rating. A matching threat family does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.