>>1027229
I'm reposting this since OP is trying to slide it.
This explains why this is different:
>>1026128
Specifically these parts:
>Botnets, cryptocurrency miners, infostealers, keystroke loggers, remote administration tools, spyware, and trojans all have one common function: they turn infected computers into servers. It's their main function, and how they phone home. Some of the most severe security vulnerabilities in CISA's KEV catalog are for computers set up as servers, vulnerable because they're set up as servers. If apps like art programs and music makers phone home, it's weird. Servers are designed to phone home, making them perfect carriers for malware.
>These are untrustworthy files. They're black boxes with closed sources, uploaded to MEGA like lots of malware, then linked on anonymous imageboards, by literally who, with no identity or trusted reputation, who faces no deterrent, as like Pfizer and Moderna, he's not legally accountable if he harms you. Nor socially accountable, either. The untrustworthy files turn your computer into a server, exactly like malware does. The most common carrier for a malware payload is a popular program or game, and Minecraft's the most popular game.
>Instead, this literally who acted like malware distributors. He started a whole topic outside the Minecraft thread to bring special attention to these untrustworthy files, then occupied it for a day to slander the skeptics. He refused to acknowledge or softened dangerous risks, attacked risk assessors as stupid buyfags and lazy niggers, pretended they're all one Microsoft employee, oversimplified high entry barriers to being safe, spammed MEGA links at least 4 times in different threads, and kept pretending antivirus scans prove a negative, when >>1025951 "antivirus programs can never prove something clean, they only evidence detected files as more suspicious. Script kiddies have a trivial time turning malware fully undetectable by antivirus programs, and some tutorials to do so only take a minute to follow."
A game night by a trusted person like Zoom that links to trusted, verified, or open sources for files and that isn't the most popular game has much lower risk. I still wouldn't join, but it's not the same.
Running a file in a VM and sniffing packets was addressed here:
>The gold standard to run games in a secure way may be PCI passthrough via OVMF of a secondary GPU to an offline VM in QEMU, at a cost of high barriers to entry in technical knowledge and time. You can't secure servers like this, because server machines must be online. A compromised online machine is a gateway to your entire network and many YouTubers made careers messing with Indian scammers by compromising their entire network from one online machine.
So you not only can still get infected, but sniffing packets doesn't prove anything when a bad actor can shut off the phone home function for the test period. You're calling for "proof" which isn't proof.
You're obviously the OP, too. Half this thread is you. You already said this here:
>>1026161
>run it in a virtual machine so you can scan the network traffic to show how it's phoning home to some russian botnet
Then you repeat it here on another identity:
>running it in a vm and sniffing packets to show it's phoning home to a botnet
You talk about FUD on a third identity here:
>>1026127
>assmad and spreading FUD
And here:
>>1027217
>you're just being a fudnigger at this point
And it was noticed that identity made this post:
>>1026133
>Hey retard who forgot to take his ratilin, where the fuck are you on game night threads?
Which talks about game nights like you do here:
>1027217
>a lot of gamenights were done solely to distribute malware
And on ANOTHER identity here:
>>1026181
Which accuses people of samefag, because it's what you're doing:
>>1026190
>Samefag
And the same specific medication you talk about here:
>>1026133
You talk about on another identity here:
>>1025858
And the identity posting the zzz links, f273ae, says most of what you're saying here.
>>1027217