Author Topic: Superuser flagged as PUP - help me deal with it please  (Read 3064 times)

0 Members and 1 Guest are viewing this topic.

cooby

  • Guest
Superuser flagged as PUP - help me deal with it please
« on: June 09, 2013, 09:07:53 PM »
On one Thrive tablet I have Avast 2.0.4675 and Superuser 3.0.7, .bin 3.0.3.2.
Avast definitions are current, but the version is not, my fault.
Superuser got flagged, big alert, as Android:ZergRush-B(PUP)
I reanylyzed at VT today - is clean (just Vipre says is not)
https://www.virustotal.com/en/file/8135f47bab91a26adfd563ed4dd22e25f454dfae02a076b6f3cd05604f2068a8/analysis/1370804039/
 
I did allow AMS to gather a report but it won't be of any use to you considering I'm behind on updating.
Here's the problem
1. I can't kill Superuser, it's essential on a rooted system, but the only option in the AV I see is to uninstall - that I really can't do, I think.
2. I do need to update Avast to the current version which isn't alerting.

Please advise what steps I should now take and exactly in what sequence.


---------EDIT: there are several superuser applications around. The one I referenced here was
com.noshufou.android.su-41-v3.0.7.apk
current version, according to google search and another tablet here, is
com.noshufou.android.su-46-3.1.3.apk

« Last Edit: June 30, 2013, 05:33:32 PM by cooby »

cooby

  • Guest
Re: Superuser flagged as PUP - help me deal with it please
« Reply #1 on: June 13, 2013, 03:28:32 AM »
Thanks for the answers :)

It seems to have fixed itself with subsequent definition update, so no longer is there the red alert.
Is that how it normally works? If so,that;s pretty nice.

Offline Filip Havlicek

  • Avast team
  • Massive Poster
  • *
  • Posts: 2647
Re: Superuser flagged as PUP - help me deal with it please
« Reply #2 on: June 13, 2013, 07:30:00 AM »
Hi,

I sent this topic to our viruslab so they probably took care of it and forgot to write something here :) Yeah, that's how it works, if it's a false positive, it gets fixed in the definitions and then automatically in the app (actually one of the shields is usually responsible), the same applies if some new malware is discovered and added to the definitions.

Filip