Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Here's ChatGPT's thoughts on the topic.  It also gave me a bunch of suggestions for steps I can take, so I'll be trying those out this weekend and reporting back what I can learn:

Possible Causes

  1. Heuristic Detection:
    • Some antivirus programs use heuristics to flag behaviors that might resemble malware, such as:
      • Frequent updates or changes to the executable.
      • Accessing low-level system resources.
      • Packing or compressing the executable to reduce size.
  2. New Build Misidentification:
    • If the recent build contains code that is new or altered in a way unfamiliar to antivirus databases, it might mistakenly flag it as a threat.
  3. Generic Threat Name:
    • The designation "DefenseEvasion.A!ml" suggests Windows Defender or another antivirus has classified the program as a generic potential threat, often without specifics. It may just be that certain code patterns or file behaviors resemble malware.
  4. Executable Compression or Obfuscation:
    • If you're using tools like UPX to compress your executable, antivirus software can incorrectly flag it as malicious because such tools are often used by malware creators to hide their code.

I don't think this will be all that helpful in determining what the issue was but after I removed the file from quarantine, it now runs without triggering the issue, which also means I can't replicate it to see if there's any additional information that might point to the problem.

I think it's a false positive.  Over the years, grabbing random roguelikes from around the internet, I often get them.  Apparently lesser known files can trigger some virus detectors just by virtue of being lesser known.  Let me know if anything else pops up, and I'll see if anyone else chimes in with the issue.  But I just ran about 60 different tests to see if I could determine anything amiss, and it's checking out as fine no matter what angle I take.  Thanks again for bringing this to my attention!