What should be detected as JS:iframe-[XX] is surprisingly, not detected–by any antivirus.
Based on the exploit given here: http://forum.avast.com/index.php?topic=96822.0
In which, is dated one month ago, I would assume that the AV industry would be able to block this kind of threat.
The appendChild iframe attack method you described had already been known to us from around the year 2008. From the moment a user clicks only the iFrame URL is changed, and JS malware contol is being maintained through this invisable full-screen iFrame. The URL bar that does not change with each click, being the only drawback when this attack method is performed…
Please don’t publish links to malware on file share sites as this is a publicly available forum and you have no control over who might download it or what they might do with it. Samples should be sent directly to avast and not shared.
So I would advise its removal from the posts and from the file share site.
Agree with you here, that is why I sometimes even break scan result links now. In a public forum be aware that the malversant is reading over your shoulder all the time.
Still there should be room for some criticism here, because as this type of malware is a recycled 2008 type, coming right out of the widely available txt-books (also to be googled and read online) it is a shame really that it is not being detected by a wide variety of av solutions. Apparently priority went to file viruses and trojans and scripting threats held a lower priority for quite some time. Avast is certainly catching up in this respect, other av’s certainly lack behind. And some even admit this,
I think script anomaly detection and IDS incorporation should come to av detection asap. We cannot only rely on Opera and Google Safebrowsing blocking inside FX and Chrome, because hordes of Blue E users will be unprotected. I have to admit that both Bitdefender TrafficLight and WOT blocks a lot of sites where this is.
Only last year Google blocked 134 million ads of which a portion were malvertizing ads. I know malware protection is mainly reactive,
The file 'JS-Iframe-Exploit--Default-DE-Compressed.js' has been determined to be 'MALWARE'. Our analysts named the threat JS/IFrame.agi. The term "JS/" denotes a Java scriptvirus. Detection will be added to our virus definition file (VDF) with one of the next updates.
The file 'JS-Iframe-Exploit--FULLY_Beautified.js' has been determined to be 'MALWARE'. Our analysts named the threat JS/IFrame.agi. The term "JS/" denotes a Java scriptvirus. Detection will be added to our virus definition file (VDF) with one of the next updates.
A very good analytical job from !Donovan, thanks to him for delving this up and also thanks for the reporting to the av community,
Pondus, so they are aware an have added this to detection,
Agree,for some reason they are being slow from past 5 to 6 days in adding samples…normally they are quick…but its getting frustrating i have 65 missed samples for avast to add detections for