CheatSpecter

A real-time modding tool for jailbroken PS5 consoles that runs in a web browser. Load one small payload on the console, open a page on your phone or computer, and switch cheats on, or find and make your own.

Use at your own risk. CheatSpecter changes the memory of a running game, which can crash it or damage a save. It has only been tested on one jailbroken PS5, on firmware 13.60. What you do with it is your responsibility.

Quick start

You need a jailbroken PS5 that can load ELF payloads, with ps5debug-NG running, and any device with a browser on the same network. Prerequisites has the details.

1. Download cheatspecter-v<version>.elf from the Releases page.
2. On the PS5, start ps5debug-NG (etaHEN can start it from its toolbox).
3. Send the ELF to the console the way you load any payload, for example by uploading it in a payload manager.
4. A notification on the TV shows an address. Open it in a browser on the same network: http://<PS5 IP>:8744
5. Start a game. Cheats made by the community for that game appear as switches on the Cheats tab. To make your own, press Guide me through my first cheat.

The payload has to be loaded again after each reboot, like any payload. Nothing is installed on the device you browse from.

No console to hand? npm install && npm run demo runs the app against a pretend PS5 so you can click around. See Installation for that and for running the app from a computer instead of the console.

What it does

Use cheats

• Community cheat tables for the running game are looked up online and shown as switches. Before a cheat is switched on, the game's memory is compared with what the table expects, so a cheat for the wrong version is left off instead of corrupting the game.
• Your game library, with a Start button for each game.
• Save your own cheats to the PS5, where they load by themselves for that game, or to your device as a .cspector file.
• Mark a cheat Keep on and the PS5 applies it every time the game starts, with no browser open.
• Restore everything puts back every change in one go.

Make cheats

• Find a value: a number you can see, a bar with no number, text, several values that sit together, or whatever changed between two moments.
• Find the code that changes it, and switch that code off: a cheat that lasts across restarts, and can be made to survive game updates.
• Code cheats with decisions ("only for the player"), built from a plain rule or written in assembly with labels and variables, and scripts in JavaScript.
• Debug: pause the game, set breakpoints, step, read and change registers, and compare objects field by field.
• Engine names: for Unreal, Unity, Godot and GameMaker games, and C++ games that keep class names, objects and fields are shown by name.

Learn

• Twelve short lessons with a practice game that runs in the page, so every step can be tried with no console and no risk to a real game.

| | | | --- | --- | | | |

Documentation

The wiki has the full guide:

| To do this | Read | | --- | --- | | Check what you need | Prerequisites | | Install on the PS5 or run from a computer | Installation | | Make a first cheat | Your first cheat | | Use every kind of search | Finding values | | Save, group, share and keep cheats on | Making and managing cheats | | Write code cheats and scripts | Code cheats and scripts | | Pause, step and inspect | Debugging | | See class and field names | Engine helpers | | Use it from Claude | MCP server and its tool reference | | Read or write .cspector files | The .cspector format | | Fix a problem, or avoid a crash | Troubleshooting and safety | | Understand how it works, or build it | Architecture and Building from source |

What has been tested on a real PS5

CheatSpecter is young, and this list is kept honest.

Used on a real console (firmware 13.60, ps5debug-NG 1.3.2), as of 0.3.0: finding the running game with its name and icon, the game library, loading community tables, known-value searches, "what writes to this", byte patches located by offset and by pattern, and saving and auto-loading .cspector files on the console.

Tested only against the built-in simulated console so far: everything new in 0.4.0 (the Debug and Engine tabs, code cheats, text and grouped search, cheats the PS5 keeps on by itself, section "master code" cheats, the Learn page), and from earlier versions: function calls, scripts, the pointer-path search, unknown-value searches, starting a game from the library and PS4 titles. That is why 0.4.0 is published as a pre-release. CHANGELOG.md has the detail for each version.

Where cheat tables come from

Tables are read at runtime, by your browser, from these community collections in their original location. Nothing from them is copied into this repository.

• etaHEN PS5 Cheats
• GoldHEN Cheat Repository
• HEN Cheats Collection

All three formats they publish are read: JSON, SHN and MC4.

Contributing

Bug reports, lessons and code are welcome. Start with CONTRIBUTING.md. To report a security problem privately, see SECURITY.md.

License

GPL-3.0-only, matching ps5debug-NG, whose protocol this implements and whose handler logic the simulated console follows. See LICENSE.