This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
How we hack; a list of anti-cheats and how we bypassed them #402
PatheticMustan
started this conversation in
(D) Developer
Replies: 1 comment 1 reply
-
hello, i just joined github , i am a user of the hacking system, but i have the outdated one and i have tried more than once to update it and it won't work. please help me, thanks |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our original aim with the prodigy hacking group was to improve the abysmal security on Prodigy. Well, we succeeded! Prodigy has tons of annoying anti-cheat features!
Here's a history of how hacking has evolved, and what it is today.
We also have a markdown file explaining our history.
PIXI Ages: 9/21/19 - 3/25/20
PIXI.game.prodigy.player.data.gold = 9e9
.Phaser Day: 3/25/20 - 3/26/20
Login.gameObj Day: 3/26/20 - 3/27/20
CanvasPool Days: 3/27/20 - 3/30/20
Cheat Dashboard Day: 3/30/20 - 3/30/20
Dark Ages: 4/01/20 - 4/07/20
EnableDebug Breakthrough: 4/07/20 - 4/09/20
Prodigy Console Prevention: 4/10/20
console.log
, hehe.Debugger Scope Ages: 4/12/20 - 4/15/20
Redirector Ages: 4/15/20 - CURRENT
Content Security Patch: 6/10/20
Script based hacks return: 8/25/20
_.instance.prodigy.player Patch: 9/17/20 - CURRENT
hack
variable in the global scope, and would overwrite clearInterval to protect it. Honestly, that was super lazy. We got around this by changinghack
to_
, which is used by lodash.Chrome Extension Releases: 10/21/20 - 11/11/20
11/11/20
.Prodigy adds SHA256 Integrity Checks: 11/13/20 - CURRENT
integrity
to their scripts so any modified scripts would be rejected.SHA256 Sumchecks bypassed: 11/13/20 - 11/19/20
So let's recap. Currently the things we're doing to bypass anti-cheats:
Beta Was this translation helpful? Give feedback.
All reactions