"Reloaded" Crack

[polonus]

Hi Asyn,

I agree with you here, that we are not to help users with such problems. I advised danny96 in a very subtle way that there is a more friendly and legit approach to get a specific dll implemented  and if he cannot take the hint and read in between the lines, then he rather deserves to go on checking his online "cracks" against anti-malware scanners, and not get any answers here  ,

polonus

[Asyn]

Hi Asyn,
I agree with you here, that we are not to help users with such problems.

Great.

[danny96]

Avira lab says it's clean.  
Virustotal users says it's Goodware. So It's False Positive.
http://www.virustotal.com/file-scan/report.html?id=d01f3a8e08b75619c5a010295cd438ca3b4718c877dae908e0c806018095a151-1321016543

[Left123]

"Can .dll files damage the system?"This is a rhetorical question i guess.
Anyhow
http://www.prevx.com/filenames/X655823274416869993-X1/RLD.DLL.html
Note: Cloaked Malware(packed,crypted etc.).In fact Jotti,gave accurate scan results.

[polonus]

Hi Left123,

Insights may differ for flagging the obfuscation techniques used, see this link: http://pesedit.com/forums/showthread.php?10424-For-AVG-users-with-rld-dll-problems&s=eeeecfa8e9d40d3dc00aaaa690fa020e&p=130860
For a VT scan on this "Battlefield Bad Company dll": http://www.virustotal.com/file-scan/report.html?id=338717b90696d61e1d938e5b27e39fa4880ace5df0f6ac7647d877258a326e9d-1267745128
where a more up to date report only comes up with 1 detection: VIPRE   10882   2011.10.26   

VirTool.Win32.Obfuscator.a which denotes VirTool:Win32/Obfuscator are detections for programs that have had their purpose obfuscated to hinder analysis or  detection by anti-virus scanners. They commonly employ a combination of methods including encryption, compression, anti-debugging and anti-emulation techniques.

But again

they commonly employ a combination of methods including encryption, compression, anti-debugging and anti-emulation techniques.

Quotes taken from MS Malware Protection Center Threat/Encyclopedia
So I cannot repeat this, but here we get a POSSIBLE infection: http://r.virscan.org/f7e1c1a1f4837b6c345574bb4932d65e

polonus

[Left123]

Hi Left123,

Insights may differ for flagging the obfuscation techniques used, see this link: http://pesedit.com/forums/showthread.php?10424-For-AVG-users-with-rld-dll-problems&s=eeeecfa8e9d40d3dc00aaaa690fa020e&p=130860
For a VT scan on this "Battlefield Bad Company dll": http://www.virustotal.com/file-scan/report.html?id=338717b90696d61e1d938e5b27e39fa4880ace5df0f6ac7647d877258a326e9d-1267745128
where a more up to date report only comes up with 1 detection: VIPRE   10882   2011.10.26   

VirTool.Win32.Obfuscator.a which denotes VirTool:Win32/Obfuscator are detections for programs that have had their purpose obfuscated to hinder analysis or  detection by anti-virus scanners. They commonly employ a combination of methods including encryption, compression, anti-debugging and anti-emulation techniques.

But again

they commonly employ a combination of methods including encryption, compression, anti-debugging and anti-emulation techniques.

Quotes taken from MS Malware Protection Center Threat/Encyclopedia
So I cannot repeat this, but here we get a POSSIBLE infection: http://r.virscan.org/f7e1c1a1f4837b6c345574bb4932d65e

polonus

I think that,an obfuscated code/progame ALWAYS wants to hide something.So,why would i trust it?Prevention is the best anti-virus.