new generation of facebook viruses

welcome all , this subject is for advanced users only , I dont think beginners will find any interest with it .

lets begin with tech stuff .
the virus is spreading as chat message or facebook event , mainly with “see who visited your profile” , the virus usually asks users to copy certain code and paste it to addressbar of the browser , the url “infact java order” triggers java file “.js” on other server , and it uses facebook window as “child window” under that file “or something like that , I am not java specialist”

the code wanted to put in the address bar


**REMOVED**

obviously triggers “topviewz.info/fb.js”.
the first version of this virus was in plain java code , this version contain encrypted code too.

thank you.
IraqGeek

Ideally any exploit code should be an image to prevent any possible alert by avast!

Even in a code tag, whilst it doesn’t parse the code on the page, it doesn’t stop the web shield when it scans the page code it isn’t parsing it just looking for exploits, etc. So if this was something detected by the web shield then it would effectively be locking us out of the topic.

You can use this image to replace the code tag.

Nothing to stop you sending this .js file to avast for analysis.

sorry - it is the second time this day :slight_smile: - still not know the rules .
about the code , I thought that I can find someone who can think with me about some way “maybe manually” to stop the spreading.
thank you anyway.

As you are an iraqgeek you should follow DavidR’s advice.

Your yahoo.com is showing and can be harvested by spammers.

There are no hard and fast rules, it is just safety first really, especially when using examples of exploits, etc. You would be surprised how many times avast alerts on such exploit code in other sites/forums.

Short of sending the .js file/exploit code to avast, virus at avast dot com email address or from the chest.

If you are interested in personally stopping it in your regular browsing, I would say firefox with the NoScript and possibly RequestPolicy add-ons, should stop such exploits dead in their tracks if avast didn’t detect the exploit.

This particular thing, is more a spam issue than a virus issue, since the js file that it invokes, causes automatic message/chat/event sending, thus perpetuating the cycle.

As far as I can tell, there is not much more to it, but I don’t see why there wouldn’t be.

I think Facebook need to look into preventing the external posting etc…

I’m sure that installing Firefox for a Newbie would be more daunting than just fixing the situation!

Well currently it is spam related, but there is nothing stopping the external posting being used for malicious purposes, cross site scripting, etc. Hence my comment about using RequestPolicy.

Total and utter hog wash, no more difficult than installing any other program, so stop spreading the FUD.

Since an end user can’t fix it they have to take precautions.

I agree, and I am not completely sure, but I think that NS would prevent the js file from working correctly (Cross Site Scripting part of it) But it doesn’t stop those who don’t know about Firefox/NS or even about the general no-nos regarding said script in the first place.

Yeah, you would know ::slight_smile:

Yep, education, education, education as TB would have said ;D

Which is why the avast! web and network shields are so important.

Site that is triggerend also re-directs to hxtp://widgets.amung.us/tab.js which is listed for ad-tracking, see:
http://hosts-file.net/?s=widgets.amung.us ,which service can be considered benign, but some have it blocked rather…
With no-script and RequestPolicy active you would not have to worry about this,

polonus

thank you all for commenting .

I’ve Installed No-Script , the problem is , you must allow script on facebook , or else you will not be able to use it!

thanks in advance.
*I hided my mail , I thought it will be hidden by default .
**I’ll send the link to avast team , so they can make an anti for it , and maybe they know the pattern and make some update to stop this method for future attacks.

Hi iraqgeek,

There is no problem to partially allow NoScript for a trusted site, but then it will continue to block redirects to elsewhere and eventual malcode, so you are still being protected, or you have to specifically allow script for the malcode site/tracking site as well, similar for the NotScripts extension in GoogleChrome allow one, block others. On this forum you can only allow/block one that is for avast dot com. It is all not that very complicated to do and will even protect from future script exploits and that is a reassuring thought, isn’t it.

polonus