From arc-probe
Injects ARC Probe into a running Windows process by name or PID, verifies TCP connection, and enables commands for memory dumps, disassembly, and pattern scans.
npx claudepluginhub vzco/arc-probe --plugin arc-probeThis skill uses the workspace's default tool permissions.
Inject ARC Probe into a running process and verify the connection.
Provides reverse engineering reference for ARC Probe: safe memory read/write, address validation heuristics, instruction patching (NOP/INT3/RET), and binary identification. For process probing sessions.
Detects and analyzes malware process injection techniques like DLL injection, process hollowing, APC injection, thread hijacking using Volatility memory forensics, Sysmon events, and API monitoring.
Detects and analyzes malware process injection techniques like DLL injection, process hollowing, APC injection, thread hijacking via memory forensics (Volatility), Sysmon, and API monitoring. For EDR alerts and in-memory threats.
Share bugs, ideas, or general feedback.
Inject ARC Probe into a running process and verify the connection.
target (required): Process name (e.g., "notepad.exe") or PID (e.g., "12345")Verify the target process is running:
tasklist /FI "IMAGENAME eq <process_name>" /NH
Or for PID:
tasklist /FI "PID eq <pid>" /NH
Run the injector with the target:
probe-inject.exe <target>
The injector is located in the ARC Probe build output directory. If the path is not in PATH, use the full path.
Wait 2 seconds for the DLL to initialize and start the TCP server.
Verify the probe is connected:
probe.exe "status"
Or via MCP: probe_status. This should return process info including PID, module bases, and driver status.
If probe_status fails:
netstat -ano | findstr :9998%TEMP%Report the initial status to the user, including:
After successful injection, you can send commands via:
probe.exe "<command>" — returns JSON127.0.0.1:9998, send command\nPOST http://localhost:9996 (requires GUI running)Good first commands:
probe.exe "status" # Process info, PID, modules
probe.exe "modules list" # All loaded DLLs with base addresses
probe.exe "ping" # Health check
Then explore with:
dump <addr> <size> — hex dump unknown memoryread_int <addr> / read_float <addr> / read_ptr <addr> — read typed valueswrite_int <addr> <value> / write_float <addr> <value> — modify valuesdisasm <addr> [count] — disassemble codertti scan <module> — discover C++ classespattern <bytes> [module] — search for byte patterns