Go to bottom

Harmful code in demos?

category: general [glöplog]
Oh good, so you didn't discover the hungarocoin miner tsr in there yet? :D

Guess why it is called "for (int ....)"!
added on the 2020-09-29 00:13:33 by T$ T$
added on the 2020-09-29 14:30:34 by sagacity sagacity
Keops is working for the french baguette mafia anyways ...
added on the 2020-09-29 19:22:48 by EvilOne EvilOne
1. create 4k procedural gfx
2. hide GPU crypto miner in the loader (that will be anomaly long)
3. make it popular
added on the 2020-10-01 12:40:15 by Tigrou Tigrou
Just like any software release, malware (née viruses) can creep into release files due to the nature of any upload. As in: the uploader may have malware infecting his upload without him knowing about it..

Antiviruses complaining that e.g. a PC intro is suspicious though, is only due to silly generic virus software by people who have no clue and don't scan binaries for actual suspicious code. It goes by other generic things, such as extensions, file size, etc.

It would take too long to for any antivirus to scan a binary *properly*, so antiviruses don't do it.

A much better scan is downloading a demo from a demoscene website. If it's too big, if something was appended, this will be remarked on for intros and quickly resolved. For demos, the only source of a virus injection is if it runs on a *very* popular public engine or compiler library of some sort.
added on the 2020-10-03 22:37:53 by Photon Photon
Well, when I started this thread back in the prehistoric days of humankind I was thinking more in the lines of malicious code inserted in the prod by the authors of said prod and not some unrelated virus infecting the file. Perhaps demo makers should start supplying checksums or digital signing or something? :) Then you'll know if you'll get the original malware or not.
added on the 2020-10-04 11:04:06 by El Topo El Topo
Checksums won't help if a virus infected your compiler ;)


Go to top