skills/electron/SKILL.md
Use when running beta Electron Team profiles against a local Electron app, extracted app.asar, or desktop application source, including Electron config, preload bridge, IPC, custom protocol, and research-note-assisted prompt preparation.
npx skillsauth add ghostonbutterbread/bug-bounty-harness electronInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run beta Electron Team profiles through the normal BaseTeam storage, review, and ledger flow.
/electron <program> <target_path> [--profile <key>] [--research-context <path>] [--dry-run-prompts] [--prepare-prompts]
Examples:
/electron canva /home/ryushe/Shared/binaries/canva/exe/input/app_asar --dry-run-prompts
/electron canva /home/ryushe/Shared/binaries/canva/exe/input/app_asar --profile electron-preload-bridge-hunter --research-context ~/Shared/binaries/canva/exe/appmap --prepare-prompts
Read the playbook before running or preparing prompts:
$HARNESS_ROOT/prompts/electron-playbook.md--research-context paths$HARNESS_ROOT/prompts/electron-playbook.md$HARNESS_ROOT/agents/electron_team.py$HARNESS_ROOT/agents/electron_profiles/~/Shared/binaries/{program}/exe/program and local target_path.cd "${HARNESS_ROOT:-$HOME/projects/bug_bounty_harness}"
PYTHONPATH="$PWD${PYTHONPATH:+:$PYTHONPATH}" \
python3 agents/electron_team.py <program> <target_path> --dry-run-prompts
python3 agents/electron_team.py <program> <target_path> \
--research-context <notes-or-research-path> \
--prepare-prompts
python3 agents/electron_team.py <program> <target_path> --agents static
electron-config-auditorelectron-preload-bridge-hunterelectron-ipc-protocol-hunterList profiles with:
python3 agents/electron_team.py --list-profiles
zero_day_team flow.documentation
Use when attacker-controlled input is saved and rendered later in a profile, comment, title, notification, admin view, export, email, feed, upload metadata, or other stored render surface.
content-media
Use when attacker-controlled input appears in the immediate HTTP response or browser-rendered page and needs reflected XSS context classification, payload selection, mutation, and browser verification.
data-ai
Use when inspecting proxy traffic from PwnFox-profiled browser sessions, filtering Caido/Burp/proxy history by X-PwnFox-Color, or interpreting user phrases like 'Red session' as a distinct browser/auth/profile lane.
tools
# LFI — Local File Inclusion Bypass ## What It Does Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning. Load `general-security-testing-policy`, `live-testing-policy`, and `injection-testing-policy` before live testing. For file/path sinks, absence of an immediate file read or response delta is not a stop reason by itself; use the policy to reason about path normalization, extension allowlists, wrappers, encoding, parser differences, and stack-specific proof ladder