See: htxp://zulu.zscaler.com/submission/show/308d3b05fc7c44a25c2d759cf953e1b6-1339675726
and
htxps://www.virustotal.com/url/5983a1403a9851d98cf53e7c6e7ac7d9ed95f8f1b2efe70f74ecc1bab02934f2/analysis/1339675775/
and
htxps://www.virustotal.com/file/a127267d78ac692589e099399851771ababe1d6deb3c61bbc02cc1901856bdf5/analysis/1339675781/
and so I scanned here, because I did not find any avast results with VT’s for the file scan of this trojan dropper
htxp://vscan.urlvoid.com/analysis/34aa1cb0cc90f6fbd889c40e556feb90/Mzg1MzgwMzIyLW1vZHBhY2stZXhl/
I’m not convinced that the detection is good (7/41) given that all detections other than DrWeb’s detection are generic and 4 of those are the same Trojan.Generic.KD.648986 signature, now that smacks of all 4 using the bitdefender signature (GData also use bitdefender (I believe) as well as avast).
Especially as the major AV players don’t seem to detect it either.
Thank you very much for your observations. But your assumption was speculative.
Because we now have avast detection for this dropper.
Trying a Get with malzilla I got a neat blocking by the avast webshield for Win32:Dropper-gen[Drp].
We are being protected, folks. That was being implemented within the next avast update after sending.
Jolly good,