Caspr1.dll

I know what i'm going to say is OT, but i am curious.

why The Cleaner uses CASPR to unpack Aspack and Asprotect since it is an outdated reverser tool, and not an own built-in unpacker like anyone else?

 

Could someone please take a look at this thread and take a shot at why (even after the latest updates to NOD), they're still getting this result when someone's using The Cleaner? Thanks. Pete

http://moosoft.com/forum/viewtopic.php?t=2710

 

Hi Pete,

It's me Jan (FanJ).
The last time I checked it when I was at home, it wasn't indeed fixed yet.
As Marcos wrote, and Anton told me in an email, Eset will look further at it.
But it's the holiday-season so it could take some days, maybe a week.
I hope this helps a little bit.

Cheers, Jan.

 

All this fight for something it can be found explained, with just a small search and some questions. So sad. :-(

The file is first the unpacker of hacker construct, to enable piracy soft. It is later assigned by virus and trojan construct, to replace the real soft with warez soft and virus or trojan included, with no trace.

But it is old technology, well known by anti-virus people. Of course to use it places your program in danger of suspicion of virus or trojan construct. Who is at fault? Not the NOD32 or the PestPatrol. In all the world, most such use is for evil purpose.

I hope I explain to your understanding.