4 ms·
While it is true those executables may be small files, that doesn't mean they can't be part of a larger malware suite, one where the vestibulk of innocent looki
by Terr_ 3y ago
While it is true those executables may be small files, that doesn't mean they can't be part of a larger malware suite, one where the vestibulk of innocent looking code is elsewhere, and the specially-packed executable contains the damning secret sauce.
- GuB-42 3y agoThey definitely could be part of malware, that's why they are flagged as such. I know the context, I know what's in the archive with it, and I am pretty sure the executable are safe, but the scanner doesn't know, and doesn't get to see the nice effects for conformation. Most people simply turn off the scanner when dealing with these files. Scanners could discriminate. These productions are often compressed with well known packers. It would be a "simple" matter of unpacking the file and scanning the result executable, which is often just a bunch of graphics and sound calls. But that's significant work for such a niche application. These tiny packers are also way more resource hungry than their size would suggest.
- Terr_ 3y ago> These tiny packers are also way more resource hungry than their size would suggest. I wonder if that might also expose some attack-surface, like with "zip bombs".