Token Hooking & Encryption Interceptor
Budget: $750 – $1,500 USD
I need a small interceptor that can hook into an existing application, capture its authentication token flow, and then perform on-the-fly encryption and decryption of those tokens before they travel further through the stack. My priority is the token life-cycle itself, so if it is simpler for you to insert the hook at a single function, system call, or even at the library boundary, I am open to whichever technique proves most reliable and least intrusive to the host process.
Scope of work
• Inject or otherwise attach the hook so the target app’s token data can be intercepted in memory.
• Decrypt the captured token, expose it in a readable form for internal processing or debugging, then re-encrypt it with the original scheme so normal execution remains unaffected.
• Keep the host application fully functional—no crashes, freezes, or noticeable slowdowns.
Deliverables
1. Source code (C/C++, Rust, or another low-level language you can justify) with build instructions.
2. A short README explaining the hooking point you chose and how to adapt it to other builds of the same app.
3. Demo video or screenshots that show a token being intercepted, decrypted, modified (if needed), re-encrypted, and successfully accepted by the host application.
Acceptance criteria
• Tokens remain valid after re-encryption.
• The interceptor can be toggled on/off without reinstalls.
• No network or file I/O leaks beyond the described token handling.
Feel free to suggest improvements to the interception method if you see a more elegant approach.
Scope of work
• Inject or otherwise attach the hook so the target app’s token data can be intercepted in memory.
• Decrypt the captured token, expose it in a readable form for internal processing or debugging, then re-encrypt it with the original scheme so normal execution remains unaffected.
• Keep the host application fully functional—no crashes, freezes, or noticeable slowdowns.
Deliverables
1. Source code (C/C++, Rust, or another low-level language you can justify) with build instructions.
2. A short README explaining the hooking point you chose and how to adapt it to other builds of the same app.
3. Demo video or screenshots that show a token being intercepted, decrypted, modified (if needed), re-encrypted, and successfully accepted by the host application.
Acceptance criteria
• Tokens remain valid after re-encryption.
• The interceptor can be toggled on/off without reinstalls.
• No network or file I/O leaks beyond the described token handling.
Feel free to suggest improvements to the interception method if you see a more elegant approach.