• We just launched and are currently in beta. Join us as we build and grow the community.

Avoiding detection with written hacks?

gabriele31

Tech Revolutionist
G Rep
0
0
0
Rep
0
G Vouches
0
0
0
Vouches
0
Posts
45
Likes
179
Bits
2 MONTHS
2 2 MONTHS OF SERVICE
LEVEL 1 400 XP
Hello Nulled, glad to be joining the community.
As my first post, I'd like to ask a question. I've recently written my first CS:GO 'hack', a simple bhop script, in C#. I have extensive experience in C#, Java and C++, so I am well versed in the languages themselves. I am just wondering what goes in to VAC detecting a cheat.
I am aware that they read signatures of well-known hacks and then ban anybody running this. However, how are these hacks detected in the first place. I have a few specific questions:
  • I have a .dll that I found online for reading and writing memory addresses. It was made in 2010 (VAMemory for anyone who was wondering), and thus I feel that this could be a weak point for my hack and lead to detection. Should I write my own memory reader/ writer?
  • Does VAC detect when you read and write a memory address? I was thinking of writing a simple ESP too for private use. However, wouldn't this be easier to detect since it is required to add a glow around players?
  • Is there anything else I should know in securing my hacks? Any general info or something that has gone completely over my head?
Good to be here,
ArriZ
 

442,401

317,942

317,951

Top