3 ms·
I anticipated this question :) No, it was just a plain Windows form, built from scratch using a then-popular Windows IDE. I think it was mostly triggered by th
by kozak 5y ago
I anticipated this question :)
No, it was just a plain Windows form, built from scratch using a then-popular Windows IDE. I think it was mostly triggered by the file name, maybe in combination with some crypto code inside.
- magicalhippo 5y ago> using a then-popular Windows IDE If you're referring to Delphi, this has been a common issue for a long time. Delphi seems to have been very popular with malware writers, and so AV companies keep flagging stuff from the standard libraries as malware. Got so bad at one time that some tried to get a deal with the major AV players to provide a suite of very basic Delphi applications they could use for false-positive testing.
- kozak 5y agoThis is so sad.
- nitrogen 5y agoNSIS installers used to get flagged as malware occasionally, too. Was very frustrating for distributing software.
- ampdepolymerase 5y agoWhat about pre-.NET VB?
- magicalhippo 5y agoThose required prerequisites in the form of the VB runtime, so AFAIK not so popular. Also more limited or difficult to use in terms of writing malware.
- ptman 5y agoDelphi produced (produces?) quite small executables, which was very desirable for malware writers.
- magicalhippo 5y agoI'd add small stand-alone executables. IIRC it was also quite popular in Europe in general, due to Pascal or Delphi being used at universities etc. In recent times your average Delphi application has gotten rather bloated, but that's mainly due to RTTI, generics and certain standard library stuff. It's still quite possible to make small executables.