Posted August 2, 200618 yr Note: No warez is used in this tutorial. The CRC32 does require a registration process, but I am providing it for you under the terms of Educational Use ONLY. That is what we're doing, checking the CRC sig for the purpose of this EDUCATIONAL tutorial. Okay people, this is reletively old news (It's about 3 or 4 days old). It was also just made public, so I have no reason to not release this anymore. The basis of this is simple: All VAC2 does to ban people is check the CRC in memory against a database of crc signitures. Simple enough, eh? There's a SIMPLE way to get around this. I will post a summary of the workaround here. You can go to vacdisabled.net (website posted for tutorial purposes only), for the full tutorial. I believe it's still up there. First, you'll need to download CRC32, upx201w, and Hex Workshop. Here's the basic, in a nutshell, overview for those who know what the fuck they're doing. Locate your hack's DLL. This will be the subject of our tampering, since this is what get's injected into memory. Copy your DLL, then move one copy into C:\upx201w. Make sure that there are no sub directories, or it will now work. Next, type cd c:\upx201w upx.exe -d [then the file name of your dll. Including .dll extension] This will decompress your dll, so you don't fuck your binary file when you hex edit it. Open the DLL with Hex Workshop (or any other Hex Editor), and change a line of TEXT. Make sure the string is the same length, or it will not recompress correctly and work with your hack (the injector won't recognize it). Make sure you are editing the ASCII values, NOT THE HEX VALUES. For example: Change "Ecstatic Cheat" to like "Ecs7at!c Ch34t" or something. Save, then recompress. upx.exe -9 [file] Open CRC32. We have to compare the CRC signatures to insure that they are different. Browse to the ORIGINAL DLL. Click the crc32 button. The following value is what VAC2 checks for. You'll see a hex value (Hex values start in 0x). This is the CRC. Now repeat for your edited DLL. You'll notice the CRC for the new dll is different. CONGRATS! YOU HAVE A VAC 2 PROOF HACK! I suggest testing the hack on an empty serv (or doing new game in cs), to make sure the hack works properly and to get it configured to your liking before you start the rage (you know rages suck when you spend the first round or 2 configuring your aimbot n shit). ENJOY! Source: Vacdisabled.net, CSH.
August 2, 200618 yr Aha. nice if it actually works, I should have classic HLH on CD somewhere props on info
August 2, 200618 yr Wow! Thanks a lot for the info! This'll come in handy with all of those unbanned accts I have.
August 2, 200618 yr Author Oh, in reguards to 40 saying about classic HLH. Any hacks that are steam patched (meaning that they will cause CS/CSS to crash upon injection) will NOT work with this work around, as far as I know. I am pretty sure the patches steam made are source code related, in so far as that the injector causes an error when injecting the dll. However, if the hack still injects but has not been patched, this will work. I have not personally verified this, and there is no quick way of doing so (since Vac2 takes some time in banning you). However, after looking over the VAC2 module ASM, crc check does seem to be the method of detection. Also, the guys over at Vacdisabled are very reliable, so if they say changing the crc of the file will work, then it will work. EDIT: I have personally used similar methods in the past on VAC2 that WERE EFFECTIVE. A couple of my private hacks I made for an old group X2N (based on leaked ECC code) were eventually leaked and detected (i guess they were leaked in order to be detected). All I had to do to avoid detection was change a couple of the string names in the hack itself, and then change some things in the injector.
August 2, 200618 yr i was just gonna post that zodiac. also hacks that use slotsfx/retart and well basically any addresses and were made before March 13, 2006 wont work [CS 1.6]
August 2, 200618 yr Author Sobeit']i was just gonna post that zodiac. also hacks that use slotsfx/retart and well basically any addresses and were made before March 13, 2006 wont work [CS 1.6] Yes, patched.
August 2, 200618 yr Author bar']old It is quite old, since I've been doing similar (but more extensive) things for over a year now, I believe. However, this method was verified by vacdisabled. It's fast an easy, and works on any hack with an external dll. This is the second public announcement of this message to such a big community (probably the biggest announcement), and to most of them.. it's going to be new.
August 2, 200618 yr Author cha0sj3ssy']wav allready released a vac disabler on both mpc and cheat-network. vac disablers hardly work as supposed to, including wav's. Eventually the hacks are still detected.
August 2, 200618 yr sure, the hack eventually get detected.. but whole purpose of vac disablers is to: still be in good standing, not to prevent public hacks from getting detected.
August 2, 200618 yr Pretty cool, except all these people who are like "yeah well good this will work for me"...idiots stop saying shit you havn't done. Just get banned the good ol`fashion way and save your sel fucking up steam accs. :) But, yeah...it's pretty cool, and for a list of hacks not dectected yet sourceindusteries.net
August 2, 200618 yr Ive feared using hacks in CS because of detection. Is their anyway I can make the hack seem diffrent from the original with out screwing it up? Like a varaition of it. This would make it sorta like a private hack and avoid all detection methods because as far as i know vac2 does not look into your cpu deeply, just scans.
August 2, 200618 yr Ive feared using hacks in CS because of detection. Is their anyway I can make the hack seem diffrent from the original with out screwing it up? Like a varaition of it. This would make it sorta like a private hack and avoid all detection methods because as far as i know vac2 does not look into your cpu deeply, just scans. yes... it scans the processor... I take it you didn't read up above.
August 3, 200618 yr Author Ive feared using hacks in CS because of detection. Is their anyway I can make the hack seem diffrent from the original with out screwing it up? Like a varaition of it. This would make it sorta like a private hack and avoid all detection methods because as far as i know vac2 does not look into your cpu deeply, just scans. Did you not read anything in my first post?
August 3, 200618 yr Author I doubt it's fully VAC2 proof, but it helps. Vac 2 only CRC checks memory being used (i.e. memory in RAM). Don't believe me, download the module and disasm it. You have to know ASM, though. This changed the CRC, making it undetectable until they get a copy of it and add the crc to their database.
