Ok, after blocking a few keylog/accsteal-attempts I had the idea to make an "File link container".
What is this?
A file link container would be a sort of box (like qoute) opened and closed with [FILE]www.google.com/virus.exe[/FILE]
This "box" has the color orange and status "Unchecked" by default.
Then, the box can either go green "Verified" (no virus) or red "Malicious" (virus)
Ofcourse, people can just post links without the [FILE] tags, people positing links to files should always use the [FILE] tags or a mod locks it.
Simple as that.
How and who will verify?
What will happen:
1. Multi-scan (VirusTotal/jotti/virscan/novirusthanks)
-> if virus detected, RED
2. Analyzing (Checking internet behavior, what files it uses, what registry codes it reads, if it creates anything (like an exe))
-> if malicious behavior is found, RED
3. If its a VB.NET application (most viruses are as vb.net as its easy to learn, and kids love being bad ass) we reflect it using reflecter or deobfuscate if obfuscated.
4. If its not VB.NET we try to decompile & deobfuscate.
If not working -> Disassembly (I have minor experience with this, but I'm learning).
Everyone who knows what they are talking about can help, I volunteer to verify and make reports. (eg. http://sythe.org/showthread.php?p=7675079#post7675079)
Thanks for reading!
thr0wback
PS: "file link container" sounds cheap, anyone has a better idea?
What is this?
A file link container would be a sort of box (like qoute) opened and closed with [FILE]www.google.com/virus.exe[/FILE]
This "box" has the color orange and status "Unchecked" by default.
Then, the box can either go green "Verified" (no virus) or red "Malicious" (virus)
Ofcourse, people can just post links without the [FILE] tags, people positing links to files should always use the [FILE] tags or a mod locks it.
Simple as that.
How and who will verify?
What will happen:
1. Multi-scan (VirusTotal/jotti/virscan/novirusthanks)
-> if virus detected, RED
2. Analyzing (Checking internet behavior, what files it uses, what registry codes it reads, if it creates anything (like an exe))
-> if malicious behavior is found, RED
3. If its a VB.NET application (most viruses are as vb.net as its easy to learn, and kids love being bad ass) we reflect it using reflecter or deobfuscate if obfuscated.
4. If its not VB.NET we try to decompile & deobfuscate.
If not working -> Disassembly (I have minor experience with this, but I'm learning).
Everyone who knows what they are talking about can help, I volunteer to verify and make reports. (eg. http://sythe.org/showthread.php?p=7675079#post7675079)
Thanks for reading!
thr0wback
PS: "file link container" sounds cheap, anyone has a better idea?
























