{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "morluto-awesome-reverse-engineering--triage-electron-app-ipc-and-bridges",
 "repo": "morluto/awesome-reverse-engineering",
 "repo_url": "https://github.com/morluto/awesome-reverse-engineering",
 "repo_slug": "morluto-awesome-reverse-engineering",
 "title": "Map IPC channels and preload bridges in an Electron app",
 "page_title": "How to map IPC channels and preload bridges in an Electron app with Awesome Reverse Engineering",
 "summary": "Use hexvero to scan an Electron archive for IPC channels and window settings.",
 "who": "A security reviewer who needs to understand how a desktop Electron app talks between its renderer and main process.",
 "problem": "Electron apps hide their inter-process messaging in large JavaScript bundles that are hard to review by hand.",
 "outcome": "A list of IPC channels, preload bridges, and window settings found in the archive.",
 "steps": [
  "Read the hexvero entry in the File identification and triage section at https://github.com/maximilianfeix/hexvero.",
  "Install Node.js 22.12 or later, as the README requires.",
  "Install hexvero by following its own repository instructions.",
  "Point the CLI at the Electron archive you are reviewing.",
  "Check the output against the JavaScript code, since the README warns that pattern-based analysis can miss indirect code."
 ],
 "agent_prompt": "Using the morluto/awesome-reverse-engineering list, summarize what hexvero reports for <electron-archive> and list the IPC channels and preload bridges it finds. Expected output: a table of channels with their source files. Verify that the report notes the limitation about indirect code.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says pattern-based JavaScript analysis can miss indirect code, so results are a starting point, not a complete map.",
 "category": "Security and science",
 "tags": [
  "Security and science"
 ],
 "lang": "python",
 "requirements": [
  "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"
 ],
 "risk": "dual-use",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.6,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/morluto-awesome-reverse-engineering/triage-electron-app-ipc-and-bridges/",
 "md": "https://dedupedai.com/use-cases/morluto-awesome-reverse-engineering/triage-electron-app-ipc-and-bridges/index.md",
 "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 hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/morluto-awesome-reverse-engineering--triage-electron-app-ipc-and-bridges.json",
 "api_version": "v1"
}