Jump to content

DrDESidran

Members
  • Content Count

    18
  • Joined

  • Last visited

About DrDESidran

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I assume that your 'machine learning' isn't machine learning by any sense of the word and that it's just a set of stupid rules. One of which is anything with a BMP extension automatically gets flagged. Oh, but what about PNGs? Couldn't malicious code be in there, too? Of course it could. Now I suppose you'll add another stupid rule that anything that ends in PNG must also get flagged. But, let's not stop there! Let's flag all resources because, technically, any of them could be used to hide malicious code. It's badly written code like this that gives machine learning and AI a bad name. You really screwed the pooch on this. Please forward this to your so-called 'devs'. And, again, this old CS prof that taught machine learning at Research 1 university gives them all a big fat F for turning in a non-working program.
  2. That's it. Just simply adding a BMP resource is all it takes. That's it! Look at the XAML code below. I have since discovered that simply changing the BMP to a PNG will thwart your mighty machine learning AI!
  3. You are completely missing the point: simply adding a BMP as a resource to a program is causing your POS 'machine learning algorithm' to flag it as a virus. This is so stupid that whoever is responsible for writing this terrible code should be fired and flogged immediately. There is absolutely no reason why adding a BMP as a resource to a Windows program in Visual Studio should cause any false positives. Simply sending you an EXE and having you register it as a 'safe program' is not a solution. It's not even a work around. It's terrible customer support and terrible business and terrible coding. I am truly disgusted by your response. Malwarebytes used to be a good product. It sucks now.
  4. Should I just tell all of my clients to set exclusion rules so they can run my programs? Because Malwarebytes is flagging the executable on other machines now. You seriously need to solve this problem NOW. I repeat, I did my doctoral research in Machine Learning and whatever you think you're doing is completely screwed up! Simply attaching a BMP as a resource triggers your brain dead 'Machine Learning' algorithm. This is terrible. As a former CS prof I'm giving you guys a big fat F (as I would to any of my students who turned in a project this messed up).
  5. Your 'Machine Learning' algorithm is barfing on simply adding an image with a BMP source! I'm using Visual Studio 2017. I've attached a screen shot with the 'offending line' commented out. This is a very common thing to do! Jeez!
  6. Further investigation shows that your Machine Learning is barfing on the inclusion of a BMP as a resource. This is pathetic. Please do something about your terrible Machine Learning algorithm. Seriously? Including a BMP as a resource is enough to trigger? Terrible!
  7. I'm a developer. I'm writing in C# WPF and am using Visual Studio 2017. I just added a simple new window to my program and Malwarebytes is now falsely declaring the EXE as 95% anomalous. At first, I thought it was because I had included a BMP resource, but I removed that and it's still being tagged. I've got nothing now except opening up a second window and it's still being tagged. Literally, simply creating a XAML document for another, empty, window is enough to trigger your Machine Learning. Okay, now I have to say this: My doctorate is in Computer Science. My research area is Machine Learning. And your Machine Learning algorithm really sucks. This is not the first time I have had my development stopped dead in its tracks because of false positives from your Machine Learning algorithm. Seriously. Please just remove it. It's terrible. There's no point in sending you the XAML code because it's literally just opening up another window. Please do something immediately. Malwarebytes has effectively stopped all development on this project because of your false positive.
  8. Well, try to confirm that process.start is the culprit and we'll use another call.
  9. I did a rebuild of the EXE because Malwarebytes locked the original. But the checksum should be the same. Could the call process.start to open the Wikia web page https://general-staff-wargaming-system.wikia.com/wiki/General_Staff_Army_Editor cause the False Positive?
  10. Zip file of EXE and LOG attached. EXE won't run without lots of other supporting files. FalsePositive.zip
  11. I've been using MalwareBytes since the very beginning. But, recently, we're getting plagued by false positives for our own code! I just did a build of our new game and MalwareBytes tagged it as Ransomeware probably because we use an online Wikia for documentation. What gives? Is this the case? How can we stop this?
  12. Dramatic? Really? As a computer science professor I would not only give the author of this heuristic an 'F' I would seriously doubt their ability to be a commercial software developer. You simply cannot release a commercial product that creates false positives like this. Think of the ramifications. Who is the user going to blame? Malwarebytes or my software? The economic consequences of a false positive could be disastrous. If Malwarebytes false positive is responsible for the loss of sales of commercial software are they legally responsible? What if Malwarebytes falsely flags mission critical or life saving software and the user then deleted the wrong program? In grad school at a Research One university you are required to take computer ethics classes. This is a text book case of a company behaving irresponsibly. Malwarebytes should immediately discontinue incorporating this heuristic.
  13. This is really a shame. For years I encouraged my students to use MalwareBytes. The heuristic you're using is badly flawed. This is an example of what my British friends call, "far too clever by half."
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.