Agent skill
electron-ipc-security-audit
Analyze Electron IPC implementations for security vulnerabilities including contextIsolation, nodeIntegration, preload scripts, and channel validation
Install this agent skill to your Project
npx add-skill https://github.com/a5c-ai/babysitter/tree/main/library/specializations/desktop-development/skills/electron-ipc-security-audit
SKILL.md
electron-ipc-security-audit
Analyze Electron IPC implementations for security vulnerabilities. This skill performs comprehensive security audits of inter-process communication patterns, checking for contextIsolation issues, nodeIntegration risks, preload script security, and IPC channel validation.
Capabilities
- Audit IPC channel implementations for security vulnerabilities
- Check contextIsolation and nodeIntegration configuration
- Analyze preload scripts for unsafe patterns
- Validate IPC message handling and sanitization
- Detect prototype pollution risks
- Check for remote code execution vulnerabilities
- Review Content Security Policy headers
- Identify exposed APIs through contextBridge
Input Schema
{
"type": "object",
"properties": {
"projectPath": {
"type": "string",
"description": "Path to the Electron project root"
},
"auditScope": {
"type": "array",
"items": {
"enum": ["ipc-channels", "preload-scripts", "main-process", "renderer-security", "csp", "all"]
},
"default": ["all"]
},
"severity": {
"enum": ["all", "critical", "high", "medium"],
"default": "all",
"description": "Minimum severity level to report"
},
"includeRecommendations": {
"type": "boolean",
"default": true
}
},
"required": ["projectPath"]
}
Output Schema
{
"type": "object",
"properties": {
"success": { "type": "boolean" },
"summary": {
"type": "object",
"properties": {
"totalIssues": { "type": "number" },
"critical": { "type": "number" },
"high": { "type": "number" },
"medium": { "type": "number" },
"low": { "type": "number" }
}
},
"findings": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": { "type": "string" },
"severity": { "enum": ["critical", "high", "medium", "low"] },
"category": { "type": "string" },
"title": { "type": "string" },
"description": { "type": "string" },
"file": { "type": "string" },
"line": { "type": "number" },
"recommendation": { "type": "string" },
"codeExample": { "type": "string" }
}
}
},
"securityScore": {
"type": "number",
"description": "Security score 0-100"
}
},
"required": ["success", "findings"]
}
Security Checks
Critical Checks
- nodeIntegration enabled: Check for
nodeIntegration: truein BrowserWindow - contextIsolation disabled: Check for
contextIsolation: false - sandbox disabled: Check for
sandbox: false - Direct ipcRenderer exposure: Check for exposing ipcRenderer without contextBridge
- Remote module usage: Check for deprecated remote module
- eval/Function execution: Check for dynamic code execution in IPC handlers
High Severity Checks
- Unrestricted IPC channels: Check for
ipcMain.on('*')patterns - Missing input validation: Check for unsanitized IPC arguments
- webSecurity disabled: Check for
webSecurity: false - Unsafe protocol registration: Check for custom protocol handlers
- Missing CSP headers: Check for Content Security Policy
Medium Severity Checks
- Overly permissive file access: Check for broad file system access
- Insecure web preferences: Check deprecated options
- Missing channel whitelisting: Check preload script exposure
- Navigation to untrusted URLs: Check navigation handlers
Usage Instructions
- Scan project structure: Identify main process, preload, and renderer files
- Check BrowserWindow configurations: Audit webPreferences settings
- Analyze IPC implementations: Review ipcMain/ipcRenderer usage
- Review preload scripts: Check contextBridge API exposure
- Validate CSP headers: Ensure proper Content Security Policy
- Generate report: Compile findings with severity and recommendations
Vulnerability Patterns
Critical: Direct ipcRenderer Exposure
// BAD: Exposing ipcRenderer directly
contextBridge.exposeInMainWorld('electron', {
ipcRenderer: ipcRenderer // CRITICAL VULNERABILITY
});
// GOOD: Expose only specific channels
contextBridge.exposeInMainWorld('electron', {
send: (channel, data) => {
const validChannels = ['file:read', 'file:write'];
if (validChannels.includes(channel)) {
ipcRenderer.send(channel, data);
}
}
});
Critical: Missing Context Isolation
// BAD: Context isolation disabled
new BrowserWindow({
webPreferences: {
contextIsolation: false, // CRITICAL
preload: path.join(__dirname, 'preload.js')
}
});
// GOOD: Context isolation enabled
new BrowserWindow({
webPreferences: {
contextIsolation: true,
sandbox: true,
preload: path.join(__dirname, 'preload.js')
}
});
High: Unrestricted IPC Handler
// BAD: Executing arbitrary commands
ipcMain.handle('execute', async (event, cmd) => {
return exec(cmd); // HIGH RISK
});
// GOOD: Whitelisted commands only
const ALLOWED_COMMANDS = ['list-files', 'get-info'];
ipcMain.handle('execute', async (event, cmd, args) => {
if (!ALLOWED_COMMANDS.includes(cmd)) {
throw new Error('Command not allowed');
}
return executeWhitelistedCommand(cmd, args);
});
Best Practices
- Always enable contextIsolation: Prevents prototype pollution
- Use sandbox mode: Restricts renderer process capabilities
- Whitelist IPC channels: Only expose necessary channels
- Validate all IPC inputs: Never trust renderer input
- Avoid dynamic code execution: No eval/Function in IPC handlers
- Implement CSP headers: Restrict script sources
- Use invoke/handle pattern: Prefer over send/on for request-response
Related Skills
electron-main-preload-generator- Generate secure boilerplateelectron-builder-config- Build configurationdesktop-security-auditoragent - Comprehensive security review
Related Agents
electron-architect- Architecture guidancedesktop-security-auditor- Security expertise
References
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
model-profile-resolution
Resolve model profile (quality/balanced/budget) at orchestration start and map agents to specific models. Enables cost/quality tradeoffs by selecting appropriate AI models for each agent role.
verification-suite
Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.
state-management
STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
frontmatter-parsing
YAML frontmatter parsing and manipulation for .planning/ documents. Provides read, write, update, query, and validation operations on frontmatter blocks in GSD markdown artifacts.
Didn't find tool you were looking for?