Jump to content

Chris Patterson

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Chris Patterson

  • Rank
    New Member
  1. After updating from 1.0.25943 to 1.0.25957, scans correctly. Scan ran overnight (approx 6 hours ago), and update must have occurred after the scan. Thank you.
  2. freelan-2.0.0-amd64-install Detected as Malware-Generic in local scan, uploading file to Virus Total returns zero results, including from Malwarebytes. freelan-2.0.0-amd64-install.zip log.txt
  3. Actually, I said that MBAM doesn't detect snap.do. As evidenced by me repeatedly running scans, expecting a different result each time (common misquote on the definition of insanity, eh? ). And for your last? Oh god yeah... I've even been one of those users. "Yeah, yeah, just install, %$## it!! ..... Ahhhh CRAP.... well, there goes tonight's sleep...." thanks again
  4. Thanks to the volunteers who responded here with helpful references and recommendations. I managed (apparently, anyway) to get this mess removed through a combination of ADW, FRST, Adware-Removal-Tool, and RevoUninstaller. So far, it's not showing any recurrence , and I'm keeping a tight eye on it. I was able to get the additional chrome directories wiped, and will most likely reinstall chrome later this week. Your statement about legal actions kinda bothers me. At one point, MBAM was the software of choice for removals, even for snap.do (as evidenced here : http://www.im-infected.com/hijac
  5. Lol yes, true. *sigh* unfortunately, some of the crapware companies have gotten very good at hiding their "optional" areas, and even some of my sharper clients have gotten tagged on occasion. I'd been trying to strip this out manually, but I'm not positive I got it all out. I did finally get a reply from my ticket, and he pointed to a couple of areas I missed when clearing chrome and firefox, so I'll check those... of course, he also told me that google liked to bundle conduit with Chrome installs, so I have to take some of it with a grain of salt... Anyway, will update here when I can get ba
  6. Someone who actually read my post, thanks I've got a ticket open, but they still hadn't replied when I started this post, although I did finally receive a response a few minutes ago. The snap.do junk has been around for at least two years, but there are updated versions on a regular basis. I'm not sure exactly how old this variant is, but I may poke the research section to see if they have any input. I did find at one point, a post where someone indicated using MBAM to completely remove an earlier incarnation, but more recent posts result in manual removal directions, and using additional
  7. Thanks, but sorry, that's not my question. I'm not asking for assistance cleaning the computer: I did that when I purchased a full license for the client, and that failed. The computer will get a factory restore, just to ensure that it is clean and ready to use again. My question was, why does Malwarebytes, the software, not recognize or (un)successfully remove the malware snap.do, which has been around for years.
  8. So, I've got several clients that I've recommended a combination of NIS and Malwarebytes to solve all their heartache, and so far, it's been pretty good so far. However, now I've got a Win8.1 PC infected with this snap.do crap, and Malwarebytes doesn't even recognize the problem. This crapware has been in the wild for 2 years, and my client wants to know why she spent money on a piece of software that won't even stop malware that's at least 2 years old. I can explain away zero-day attacks, like the Crypto-series. What I can't explain away is this software hijacking her computer that shows up
Back to top
×
×
  • 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.