Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(4 edits) (+1)

>Not as much that I fear an intentional virus, but because of sloppy developer machines

Yeah, I though about that but it doesn't change anything: a malware is still a malware. And I don't want anyone else to sumble upon this game randomly and get this.

But must admit it acts a bit different this time - the virus total results for this archive also are not the same as it was previously. Maybe author tried  to maintain executable a little to make it not that obvious? Or he tried to get rid of some malicious software from his PC, if it was not intentional.

It also might be removed by Windows defender, but why put anyone at risk at this point? This is getting ridiculous...

(1 edit) (+1)

I also have an old game that support does not seem to believe it is suspicous. I am half convinced the ddos attacks are from criminal groups trying to divert attention of staff, so they have less time to do good work on reports for suspicous games. That they do not react to reports on obvious malware for over a week is not really helpful to their users.

This case here might actually be an infected developer's machine. Maybe they used an unlegit version of rpg maker that was infected.

I think they might have closed the remote server that this malware was connecting to. The alternative would be, that the malware detected to be running in a vm and behaved orderly because of that. There are vm scanners and tactics to avoid detection in that vm and detection of such avoidance and back and forth.