Reverse engineer an old game binary to crack a restriction
A poster used Claude Code alongside Ghidra to trace a call graph across many validation sites in a 13-year-old game binary and crack a restriction. Task: Suggested implementation: Use Claude Code in Opus high-reasoning mode to analyze a legacy game binary lacking symbols or source code. The agent traces specific function call graphs, identifies validation sites across code areas, and recognizes x86 branch patterns. Human role involves initial setup, reviewing the identified logic, and validating the generated patches before release.; tools: Claude Code. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include access to the target binary and reverse-engineering tools like Ghidra. The source reliability is low due to a 403 error, so all details are unverified. Operating costs involve significant time for analysis and patching. Human approval is critical for legal compliance and technical validation before publishing any modifications..
Tools
Published on Agent Work Atlas:
Overview
A poster used Claude Code alongside Ghidra to trace a call graph across many validation sites in a 13-year-old game binary and crack a restriction.
Workflow
Suggested implementation: Use Claude Code in Opus high-reasoning mode to analyze a legacy game binary lacking symbols or source code. The agent traces specific function call graphs, identifies validation sites across code areas, and recognizes x86 branch patterns. Human role involves initial setup, reviewing the identified logic, and validating the generated patches before release.
Reported result
The proposed workflow aims to produce binary patches and modified data files to remove character restrictions, packaged as an open-source mod. Actual outcomes are unknown as the source is unavailable (HTTP 403). A measurable acceptance check would be verifying that the mod installs in under two minutes and allows any character in any playset without crashes.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include access to the target binary and reverse-engineering tools like Ghidra. The source reliability is low due to a 403 error, so all details are unverified. Operating costs involve significant time for analysis and patching. Human approval is critical for legal compliance and technical validation before publishing any modifications.
Try it
Act as a reverse-engineering assistant. I have a legacy game binary [replaceable: file path] with no symbols. Use Claude Code in Opus high-reasoning mode to trace the call graph for [replaceable: target function name]. Identify all validation sites and x86 branch patterns. Generate a list of potential patch locations. Do not apply patches yet. Output a JSON report with function addresses, branch conditions, and suggested patch bytes. First, perform a dry run on a small, known open-source binary [replaceable: sample file] to verify your analysis accuracy. Wait for my confirmation before proceeding to the main target. If the source is unavailable, state 'Analysis blocked' and ask for a Ghidra export instead.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.