December 19, 2012 at 2:56 pm #8080
So someone I know got hit with some malware recently, and i’m trying to understand exactly what happened, as best I can. Heres the sequence.
non admin User downloaded a zip file, and scanned it with MSE. While MSE didnt alert (strangely) it did in fact detect a trojan in the zip file and it was supposedly removed.
After the scan the user preceded to unzip the supposedly now clean zip file. This triggered some kind of malware that killed MSE, User immediatly took remediatory action.
Now, it appears to me that one of several possibilities existed… here are my thoughts:
original trojan was easily detected, was this intentional, perhaps luring the target into a false sense of security?
traditionally trojans drop files, or provide access through which further comprimise can occur. There have been no indicators of further comprimise, what am I missing?
What caused MSE to be killed? I know that commands can be executed to kill AV, but they generally require Admin or SYSTEM privlidges, user was un-privlidged. I thought maybe some sort of client side exploit to gain privlidges. I’m just not sure.
Finally, the user immediatly pulled the network cable, scanned the computer in safe mode, and regular mode with up to date scanners (3) and nothing else was detected, but can we trust this? outside of MSE which was originally killed, the other software installed at the time did not stop or detect an attack. In addition the user ran a networksniffer, and did not detect any malicious traffic after the comprimise…
December 19, 2012 at 4:36 pm #51202lorddicraniusParticipant
scanned the computer in safe mode, and regular mode with up to date scanners (3) and nothing else was detected
To be detected, this requires the malware to be known by the scanners.
December 19, 2012 at 4:39 pm #51203caissydParticipant
I know it’s not too hard to encode and obfuscate malware. Using Metasploit makes it quite easy: http://oldmanlab.blogspot.ca/2011/11/metasploit-shellcode-obfuscation-to.html
That being said, it doesn’t answer everything. I am curious to see what the others think of that…
December 19, 2012 at 4:49 pm #51204
exactly I was thinking maybe the first trojan wasn’t encoded, designed to be detected, whereas there was hidden malware that wasn’t detected.
December 19, 2012 at 8:27 pm #51205m0wgliParticipant
I’d doubt that any malware author would deliberately design something to be detected. A detection of anything would surely only increase user suspicion of what’s being installed vs an installation with no AV alert?
Even with encoding/obfuscation techniques you’re not guaranteed to bypass AV, overtime these become known to the AV vendors. Hence, why one may have been detected and not the other.
December 19, 2012 at 10:40 pm #51206
So what do you guys think happened here?
December 20, 2012 at 1:18 am #51207cd1zzParticipant
It’s certainly possible this was an 0 day on MSE. If it is, maybe the vulnerability the attacker used requires MSE to pick up some kind of virus, to trigger his 0 day exploit. Since MSE runs as SYSTEM, if you pwned it, you’ would be able to kill the service and ultimately control the box.
What’s the name of the virus it successfully caught?
December 20, 2012 at 12:13 pm #51208
It detected a trojan, i’ll have to try to have them get the name.
December 20, 2012 at 6:20 pm #51209dynamikParticipant
Is there any evidence that something malicious actually occurred when the file was extracted? Maybe MSE just crashed. Maybe your acquaintance has found the 0-day 😉
User’s will also bend the truth to avoid embarrassment. I’d get a copy and do analysis in a safe environment before jumping to grand conclusions. That’ll get you a lot farther than just speculating.
April 17, 2013 at 9:33 am #51210encryptedmindParticipant
1. This looks like a parsing bug in MSE that was exploited using a malformed zip file. A thing about the user in question is that he may have mistaken an executable file for a zip file (they come in a few variations themselves). As unzipping a zip file will not cause the contents to execute by themselves. If it was self extractable then execution could have configured. This would constitute a social engineering attack.
2. The 0 day theory is quite probable as well given the tools required for this are freely available.
3. It also could be that a malware was already running on the pre infected system and the contents of new zip files were part of its launching code. This might be in sync with your zip file extraction trigger. Malware like Flame remained undetected for years, its quite plausible a similar attack vector was being utilised.
4. Futher this could be a bug in MSE where the scanning logic is bypassed to make MSE execute the malware, based on the format trickery done on the zip.
5. Alien invasion is not really that far off…..
Ahh… so the conspiracy theory ends here…..
Any links to the malware in question, I could analyse it and give you more details.
June 9, 2015 at 12:26 pm #51211jmicgasParticipant
Even myself had doubt regarding this, thanks for sharing this here.
You must be logged in to reply to this topic.