Windows Firewall

[Veͥnoͣmͫ]

After the update today my firewall detects a "Virus" coming from Balatro

Behavior:Win32/DefenseEvasion.A!ml
file: C:\SteamLibrary\steamapps\common\Balatro\Balatro.exe

Anyone got the same problem?

[Filemon]

same here

[Death Zero]

same

[J4MESOX4D]

Just a false positive. Just whitelist the file so it doesn't trigger again.

[PokerusFreak]

Balatro after the update literally opened a window I have NEVER seen before, with a little balloon with letters on the string spelling out "no game". I closed it, very confused, tried opening Balatro again and got a windows defender popup calling it a trojan.

There is exactly zero reason any of this should be happening after an update, the game was just fine before this. Very very sus, im not chalking that up to just a false positive im sorry. What the ♥♥♥♥ was that extra program window that opened? That's pretty squarely not in the "false positive" realm

[J4MESOX4D]

Originally posted by PokerusFreak:

Balatro after the update literally opened a window I have NEVER seen before, with a little balloon with letters on the string spelling out "no game". I closed it, very confused, tried opening Balatro again and got a windows defender popup calling it a trojan.

There is exactly zero reason any of this should be happening after an update, the game was just fine before this. Very very sus, im not chalking that up to just a false positive im sorry. What the ♥♥♥♥ was that extra program window that opened? That's pretty squarely not in the "false positive" realm

No issues here with my anti-virus or the game today. Extra window could've been anything from something in-engine to do with the game for instance or the anti-virus itself. False positives happen on Steam all the time. If the AV has blacklisted the executable as evidenced by the OP then of course it will say 'no game found' or something to that tune.

[Dixego]

Yep, same here.

[Ronald Brain]

Originally posted by PokerusFreak:

Balatro after the update literally opened a window I have NEVER seen before, with a little balloon with letters on the string spelling out "no game". I closed it, very confused, tried opening Balatro again and got a windows defender popup calling it a trojan.

There is exactly zero reason any of this should be happening after an update, the game was just fine before this. Very very sus, im not chalking that up to just a false positive im sorry. What the ♥♥♥♥ was that extra program window that opened? That's pretty squarely not in the "false positive" realm

If your AV tries to scan Balatro.exe as it opens, of course the window title would become "no game". I can't say I know this engine well, but basically AV interrupts executable and scan them so the windows got stuck and the default title could very well be "no game" ('cause it can't load the window title function yet). Blame whatever AV you're using for this kind of practice, the one I use (Avast) simply show a windows saying they're scanning and close itself once it's done.

FYI, game updates usually change executable files, and if your AV is too sensitive, it will think malware/viruses altered the EXE and tried to scan again.

[Goblin]

Originally posted by PokerusFreak:

There is exactly zero reason any of this should be happening after an update, the game was just fine before this. Very very sus, im not chalking that up to just a false positive im sorry. What the ♥♥♥♥ was that extra program window that opened? That's pretty squarely not in the "false positive" realm

Did you not read the changelog? The engine got updated. The game runs in an engine that JIT compiles lua files, IE compiles the code to machine code at runtime and sends that compiled code to your CPU to run. There's plenty of reasons for changes to that "shell" program which Balatro runs in getting updated that can cause to Windows to look at the game very differently, while in reality nothing suspicious happens.
That window you noticed is what you get when you run LOVE without a program for it to run, which presumably happened as your OS was holding back access to the executable code it generated.