DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace calls in a running program with Frida with Awesome Reverse Engineering

Inject scripts into a process you are authorized to test to observe its behavior.

Authorization notice. Awesome Reverse Engineering is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Reverse engineering. Only inject into processes you own or are authorized to test, since injection can change program behavior.

Who it is forA reverse engineer or app tester who needs to see which functions a running program calls and what data they receive.

The problemStatic reading shows code paths but not the values used at runtime.

The outcomeA log of selected function calls and their data from a live process.

What you need first

  • A computer where you can install analysis tools, or a browser for web-based tools
  • A target to study, such as a sample binary you are authorized to analyze or a course lab
  • For malware or sandbox work: an isolated, disposable virtual machine and your organization's handling procedures
  • For the Electron triage tool: Node.js 22.12 or later, as the README states

Steps

  1. Read the Frida entry in the Dynamic instrumentation and tracing section at https://github.com/frida/frida.
  2. Install Frida by following the project's own setup instructions.
  3. Choose a process you are allowed to test and note the function names you want to observe.
  4. Write a small script that hooks those functions and logs their arguments.
  5. Run the script against the process and confirm that the logged calls match the program's visible behavior.

Prompt for your agent

Using the morluto/awesome-reverse-engineering list, confirm that Frida is listed under Dynamic instrumentation and tracing, then outline a Frida hook plan for the process <target-process>. Expected output: a short plan listing the functions to hook and what to log. Verify that the plan only targets a process the user is authorized to test.

Caveat. The README describes Frida only in one line, so you will need the project's own documentation for hooking syntax.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page