| name | game-rpc-pentest |
| description | Analyze and exploit custom UDP RPC protocols in games. Use this skill whenever you need to enumerate proprietary game networking protocols, intercept file-transfer RPCs, perform path traversal attacks on game saves, or turn protocol vulnerabilities into code execution. Trigger this for any game security research involving custom binary protocols, multiplayer save synchronization, or asset manipulation attacks. |
Game RPC Protocol Pentesting
A skill for analyzing and exploiting custom UDP RPC protocols in games, particularly those with proprietary networking stacks.
When to use this skill
Use this skill when:
- You're analyzing a game with custom UDP-based networking
- You need to enumerate RPC methods in a game's networking DLL
- You're investigating file-transfer vulnerabilities in multiplayer games
- You want to perform path traversal attacks on game save systems
- You're researching how to turn protocol vulnerabilities into code execution
- You're doing CTF challenges or security research on game protocols
Core Workflow
1. Map the RPC Surface with Frida
Many games embed home-grown RPC stacks on top of UDP. The goal is to enumerate all remotely reachable methods without traffic captures or symbol leaks.
Step 1: Identify the networking DLL
- Look for DLLs with names like
NetComEngine*.dll, Network*.dll, RPC*.dll
- Search for exported functions that handle message dispatching
- Look for functions with names like
RMC_CallMessage, DispatchMessage, HandleRPC
Step 2: Find the dispatcher and helper functions
- The dispatcher typically parses fields like: ID (RPC verb), Flags (transport modifiers), Source (caller object ID), TargetObject (remote object), Method (method index)
