Author Topic: (Solved) Why didn't Avast Quick Scan  (Read 7106 times)

0 Members and 1 Guest are viewing this topic.

Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
(Solved) Why didn't Avast Quick Scan
« on: May 09, 2016, 01:38:00 PM »
find this PUP?
« Last Edit: May 09, 2016, 11:21:03 PM by -midnight »
.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37650
  • F-Secure user
Re: Why didn't Avast Quick Scan
« Reply #1 on: May 09, 2016, 02:11:53 PM »
and the question is?




Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
Re: Why didn't Avast Quick Scan
« Reply #2 on: May 09, 2016, 02:13:53 PM »
Isn't it obvious?
.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37650
  • F-Secure user
Re: Why didn't Avast Quick Scan
« Reply #3 on: May 09, 2016, 02:16:17 PM »
Quote
Why didn't Avast Quick Scan find this PUP
would be easier if you did not post half the question in the topic title and other half in the post, but the hole question in the post

Anyway, probably because it is in a location where quick scan does not scan ... seems to be just a registry key / leftover

Quickscan = quick because it does not scan the hole computer   ;)   




« Last Edit: May 09, 2016, 02:51:20 PM by Pondus »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89431
  • No support PMs thanks
Re: Why didn't Avast Quick Scan
« Reply #4 on: May 09, 2016, 03:03:55 PM »
Isn't it obvious?

It is fairly obvious the detection is not a file but a Registry Key.
- PUP or not a registry key without the associated file is inert.

What we can't see is the complete text of the location in your image as it appears to be missing what the software is or any file name.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.7.6124 (build 24.7.9311.855) UI 1.0.811/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
Re: Why didn't Avast Quick Scan
« Reply #5 on: May 09, 2016, 03:43:56 PM »
This is the location.
.

Offline CraigB

  • Avast Überevangelist
  • Serious Graphoman
  • *****
  • Posts: 11248
  • No support PM's thanks
Re: Why didn't Avast Quick Scan
« Reply #6 on: May 09, 2016, 03:55:10 PM »
Still cant see the complete path, a screen shot from within the Quarantine would be much better.

Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
Re: Why didn't Avast Quick Scan
« Reply #7 on: May 09, 2016, 04:00:43 PM »
Registry Keys: 1
PUP.Optional.InstantSupport, HKU\S-1-5-21-2432266188-2506439190-3645350612-1001\SOFTWARE\InSTab, Quarantined, [7e57587bd1c81a1c2c9739947d86e21e],


.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37650
  • F-Secure user
Re: Why didn't Avast Quick Scan
« Reply #8 on: May 09, 2016, 04:09:04 PM »

Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
Re: Why didn't Avast Quick Scan
« Reply #9 on: May 09, 2016, 04:18:30 PM »
@Pondus,
I haven't gotten any Instant Support pop-up ads.
.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37650
  • F-Secure user
Re: Why didn't Avast Quick Scan
« Reply #10 on: May 09, 2016, 04:41:06 PM »
Quote
PUP.Optional.InstantSupport, HKU\S-1-5-21-2432266188-2506439190-3645350612-1001\SOFTWARE\InSTab, Quarantined, [7e57587bd1c81a1c2c9739947d86e21e]
avast has probably blocked or removed it some time, when you scanned now avast detected the leftover registry key

Run a scan with Malwarebytes just to be sure the crap is gone
« Last Edit: May 09, 2016, 04:42:37 PM by Pondus »

Offline midnight

  • Massive Poster
  • ****
  • Posts: 2479
Re: Why didn't Avast Quick Scan
« Reply #11 on: May 09, 2016, 05:25:30 PM »
I just run a scan with MalwareBytes and it didn't find anything.
.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89431
  • No support PMs thanks
Re: Why didn't Avast Quick Scan
« Reply #12 on: May 09, 2016, 06:38:24 PM »
Registry Keys: 1
PUP.Optional.InstantSupport, HKU\S-1-5-21-2432266188-2506439190-3645350612-1001\SOFTWARE\InSTab, Quarantined, [7e57587bd1c81a1c2c9739947d86e21e],


That is what I thought, essentially an empty/inert registry entry, without an associated file. Not to mention that this is pointing at some sort of Quarantine location - for InSTab - I have absolutely no idea what this if for or what program this is associated with.

But there are indications it (InstantSupport) could be malware related - http://www.bleepingcomputer.com/virus-removal/remove-instant-support.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.7.6124 (build 24.7.9311.855) UI 1.0.811/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Why didn't Avast Quick Scan
« Reply #13 on: May 09, 2016, 06:44:33 PM »
The reg key looks to be from a MBAM scan as Avast does not register reg keys just files

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89431
  • No support PMs thanks
Re: Why didn't Avast Quick Scan
« Reply #14 on: May 09, 2016, 07:06:25 PM »
The reg key looks to be from a MBAM scan as Avast does not register reg keys just files

Yes - that is why -midnight was asking, why didn't avast detect this.

But broken over the topic Subject and a continuation of that line in the post.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.7.6124 (build 24.7.9311.855) UI 1.0.811/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security