Kamamura: just because I have pointed out there is a potential security issue with the installation.
JMich: It's not because you pointed that out, it's the way you did.
Let's say a user in your company gets a "This site is blocked due to potential malware infection" on a site your company uses, and he comes to you claiming you have to purge the whole network due to possible infection. Would you thank him for his concern, or tell him he has nothing to worry about?
And how would you react when he kept saying that everything has to be scrubbed clean and thoroughly checked before anything other work from the company can be done, even though you've already told him he has nothing to worry about?
How would I react? Well, let's see. If a server I administer would be flagged as behaving suspiciously (doing portscans, attempting suspicious connections, launching attacks, containing malicious scripts), I would first ask the party who flagged it to provide evidence (AFAIK GOG has not done that). They should be able to provide logs containing evidence about attacks from my server, with timestamps and other details.
Then, if there is a reason to suspect the machine in question controled by someone else who can obfuscate his activities via a rootkit, intercepting system calls, etc., the machine would have to be switched off immediately, the disks removed and examined on a different machine so that the rootkit would have no chance to and affect the investigation. If the server is confirmed as compromised, forensic analysis must be done, the method of attack discovered and vulnerability identified (obsolete version of software with an exploit, misconfigured firewall, poorly chosen password, compromised private key, irregularity in network topology such as laptop bypassing firewalls, etc).
Then, the system in question would have to be reinstalled from safe installation files and data recovered from backup. Also, a report detailing the whole incident would have to be generated for future reference. Then the party who discovered the incident would be identified that the problem is resolved.
So if a user came to me complaining about "our site is blocked...", I could refer him to the report about the incident containing all the relevant evidence and steps taken to resolve the matter (if it was an insider), or to a press release that would contain excerpt of the above mentioned in a form suitable for general public.
In any case, saying "Uh... just ignore it, our servers are fine, I promise...", would never have been enough, and such negligence would probably cost me my job eventually.
If you are a single user, fine, at worst, your computer is a part of a botnet attack against Pentagon and the worst you risk is being dragged somewhere for interrogation and having your computer seized.
But if you run an online service, you have much more responsibility, because your sloppiness can affect a lot of users, and you should behave accordingly (obviously, many subjects including banks or content providers do not).
Kamamura: Why is it concerning?
JMich: My guess would be that a System Administrator that cannot distinguish between a false positive and a real threat would cost his/her company quite a lot of downtime scrubbing the systems for threats that are not there.
Oh, but he can... once he is provided sufficient evidence. He cannot, however, on blind belief alone.