Skip to content

ENG-8829 fix(network-ops): run relay/coercion tools as streaming listeners, not 30s force-kills #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thomasqbrady merged 1 commit into from
Oct 15, 2026
Merged

ENG-8829 fix(network-ops): run relay/coercion tools as streaming listeners, not 30s force-kills #177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion capabilities/network-ops/agents/pipeline/exploit-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Follow the **ad-attack-patterns** skill. Work through signals flagged by the enu
3. **AD CS Exploitation**: if vulnerable templates were flagged, request certs and authenticate.
4. **ACL Abuse**: if writable objects were flagged, use bloodyad to escalate (RBCD, shadow creds, group membership). Clean up after.
5. **Delegation Abuse**: constrained (S4U via impacket) or unconstrained (relay via krbrelayx + coercion).
6. **NTLM Relay**: start `impacket_ntlmrelayx`, then coerce with `coerce_petitpotam` / `coerce_dfscoerce` / `coerce_shadowcoerce`. Consult **ad-attack-patterns** for coercion method selection.
6. **NTLM Relay**: prefer `impacket_ntlmrelay_attack`, which starts the relay, fires coercion, and captures the result in one call — the standalone `impacket_ntlmrelayx` is a listener that blocks until it catches an auth or `relay_timeout`, so it cannot be followed by a coercion call in the same sequence. Consult **ad-attack-patterns** for coercion method selection.
7. **GPP Passwords**: if SYSVOL was accessible.

For each recovered credential, immediately:
Expand Down
2 changes: 1 addition & 1 deletion capabilities/network-ops/capability.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
schema: 1
name: network-ops
version: "2.1.9"
version: "2.1.10"
description: >
Network operations and Active Directory exploitation. Multi-agent
pipeline for autonomous red teaming with Nmap scanning, Netexec
Expand Down
2 changes: 1 addition & 1 deletion capabilities/network-ops/skills/ad-attack-patterns/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ Reference for common AD attack chains. Each pattern lists prerequisites, tool se
| Step | Tool | Action |
|---|---|---|
| Combined (preferred) | `impacket_ntlmrelay_attack` | Start relay + fire coercion + capture result in one call |
| 1. Start relay listener (manual) | `impacket_ntlmrelayx` | Listen and relay to target (SMB/LDAP/AD CS) |
| 1. Start relay listener (manual) | `impacket_ntlmrelayx` | Listen and relay (SMB/LDAP/AD CS); blocks until it catches an auth or `relay_timeout`, so cannot be followed by a coercion call — prefer the combined tool |
| 2. Coerce authentication (manual) | See coercion method selection below | Force target to authenticate to relay |
| 3. Relay captures and forwards | ntlmrelayx relays auth | Escalation depends on relay target |

Expand Down
Loading
Loading