zero k virus

Trojan:MSIL/Masslogger.VN!MTB
in portable distro
C:\Users\lobster\Downloads\zero-k-portable\Zero-K.exe
hmmm

i would totally trust Aquanim not to do any bollocks like this after deleting questions about donations or bans by mood

curious that steam is ok with virus spreading

id support to ask steam why and since when they support virus spreading and weird donation feedback policies of just ignoring, removing and punishing people for questions about their previous donations
sounds dodgy

Same here. Windows keeps deleting zero-k.exe

I had the same problem of having Windows Defender identify something about Zero-K as a virus when I tried downloading the newest update. I had to tell Windows Defender to let it go.

I don't recall this happening before so I imagine its something in the new update.

quote: does Googlefrog know when we poop now?

I mean, it's not that hard to take it one step furthur and be watching a dozen or so people poop through their webcams at once. perhaps also at 4k resolution and with high-definition audio.

who does that anyways

Zero-K virus

symptoms: a maps folder that gradually swells to 200gb size

cure: goodbye post in forum, typically followed by long regression period.

other notes: linked to heightened enthusiasm for cooked seafood

quote: Please use the defender/your antivurs system to report that this is a false positive. The only way to prevent it from labeling it.

Read about code signing, all those AV alarms are -heuristical- analysis because executable comes from an -untrusted- source(interwebs) and -unknown- publisher. When publisher is known thru a chain of trusted CA all heuristical analysis usually shuts down and only classical signature search stays which has nothing on chobby/spring

They also state there is extended validation available for 800$/3 years(200$/year) to bypass windows SmartScreen... not sure if it worths it, even basic signing should alleviate most of those problems

Basically when executable is signed it allows to
- verify publisher's identity(which gets recorded by CA that gives u the certificate)
- ensure that executable has not been modified since the time it's been signed by publisher

Those 2 are enough to ensure it's not a malware, and if it is means certificate been stolen/publisher went rogue => certificate can be blocked/revoked.
Reduces malware spread by 99.99%