[SOLVED] ClamAV found an infected file... should I use Darik's Boot and Nuke?

derezion,

I think you're overthinking this, the link you have posted talks about clearing the cache (which you appear to have already done), as well as backing up the cache (which you do NOT want to do), and creating a script for a cron job (which I don't think there is any need to do).

Your friend is correct in saying that rkhunter looks for known "rootkits" (among other things), but unless you have good reason the believe you might have one, there's probably not a lot of point in doing that. Although, it's not a bad idea to check for "rootkits" every once a while, if you're worried about having one and/or have visited unsafe sites.

I agree with the other posters in this thread that you clearly (with all respect) should look at practicing better browsing habits. That is the best way to prevent this kind of thing happening in the first place.

That said, you should be able to install rkhunter from your Linux distribution's online software repositories.

Originally Posted by derezion I didn't visit the result ondoho was talking about because I don't know if clamxav.com is safe.

it's good to be security aware, but this is vastly exaggerated.
it's just a forum.
and you already have noscript active anyhow.

like i said, javascript is about the only way malware can exploit your computer through your browser.

and even if clamav found a baddie, there's degrees in HOW bad it is. it very probably is not a rootkit.

just remove cookies & cache & offline data when closing your browser (not manually, that's in the preferences), and close it often.

Update: I also scanned with rkhunter and although it alerted me about some directories it found no rootkits.

I would use NoScript on all my user accounts but I read this article that warned against it.

NoScript and other popular Firefox add-ons open millions to new attack | Ars Technica
https://arstechnica.com/information-...to-new-attack/
by Dan Goodin - 4/5/2016, 3:02 PM

I have the latest version of Firefox so I don't know if this article applies.

Originally Posted by derezion NoScript and other popular Firefox add-ons open millions to new attack | Ars Technica https://arstechnica.com/information-...to-new-attack/

gah.
this is 2.5 years old; a LOT has happened in FF development since then.
namely, they have been working really hard on the whole sandboxing concept (that's what the whole article is really about).

also, please consider:

The researchers noted that attackers must clear several hurdles for their malicious add-on to succeed. First, someone must go through the trouble of installing the trojanized extension.

so, as always, sane usage habits are the first & most imprtant part of online security.

I have the latest version of Firefox so I don't know if this article applies.

no, it doesn't.
a quick glance on this suggests sandboxing started with version 57. i could be wrong though.