Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

pentest-input-protocol-manipulation

Estrelas2

Forks0

Atualizado3 de julho de 2026 às 09:18

Input validation and protocol manipulation assessment for injection, parser differential testing, request smuggling, method tampering, header confusion, serialization abuse, and payload mutation. Hands off to authz, business-logic, exploit, or reporting workflows when those become the owner phase.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

crtvrffnrt

crtvrffnrt/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·SOC 15-1212

SKILL.md

readonly

name	pentest-input-protocol-manipulation
description	Input validation and protocol manipulation assessment for injection, parser differential testing, request smuggling, method tampering, header confusion, serialization abuse, and payload mutation. Hands off to authz, business-logic, exploit, or reporting workflows when those become the owner phase.

Input & Protocol Manipulation

Use When

The main question is parser behavior, encoding, method override, header trust, smuggling, serialization, or injection capability.
A request transformation may cross a parser, protocol, or trust boundary.

Handoff Criteria

Hand off to pentest-authentication-authorization-review or pentest-advanced-access-control-auditor when an input anomaly becomes an authorization claim.
Hand off to pentest-business-logic-abuse when the exploitability depends on workflow state.
Hand off to pentest-evidence-structuring-report-synthesis when validation is complete.

Output Schema

Test matrix: vector, payload class, expected secure behavior, observed behavior
Validation state: hypothesis, confirmed, rejected
Minimal reproducible request set

Instructions

Identify the parser or protocol boundary being tested before crafting payloads.
Start with low-noise capability checks, then increase payload complexity only when signal appears.
Compare positive and negative controls for every high-impact claim.
Separate parser anomalies from exploitable security outcomes.
Record exact request transformations required to reproduce behavior.
Escalate to exploit execution only after deterministic primitive confirmation.

Verification Gate

Use structured payload families and deterministic sequencing.
Preserve request/response evidence with context and timing.
Keep tests bounded and reversible by default.
Treat status-code differences as leads until a security effect is proven.
Use positive and negative controls for every high-impact claim.
Cross-check parser behavior with a different content type, method, client, or boundary when ambiguity remains.

Mais deste repositório

mesmo repositório

pentest-shodan-helper

crtvrffnrt/skills

Shodan CLI-only search workflow for query design, filter selection, count/stats validation, and search-result retrieval through /root/.local/bin/shodan.

2026-07-082

pentest-cve-reverse-engineer

crtvrffnrt/skills

Manual vulnerability research skill for finding advisories, downloading affected and fixed artifacts, diffing patches, confirming root cause, and writing reliable reports across products and technologies.

2026-07-082

pentest-gemini-sub-htb

crtvrffnrt/skills

Controlled lab skill for Hack The Box, CTF, and private lab workflows from reconnaissance, enumeration, vulnerability research, exploitation, foothold, and privilege escalation through evidence consolidation.

2026-07-032

incident-response-fileanalyser

crtvrffnrt/skills

Static malware reverse-engineering and threat-intelligence triage for unknown files, Windows EXE/PE binaries, scripts, archives, ISOs, JavaScript, PowerShell, documents, and unpacked payloads. Use when a user provides a sample path, hash, filename, or file and asks whether it is malicious, benign, suspicious, contains IoCs, or should be reverse engineered with Ghidra, strings, capa, YARA, public TI, and structured phase artifacts.

2026-07-032

incident-response-bec

crtvrffnrt/skills

BEC and AiTM incident-response skill for suspicious sign-ins, mailbox abuse, forwarding, inbox rules, session theft, token replay, consent abuse, and secondary phishing.

2026-07-032

incident-response-main

crtvrffnrt/skills

Defensive incident-response companion for Microsoft Entra ID, Microsoft 365, Defender, and mixed identity or endpoint incidents. Use for sign-in triage, public-IP enrichment, initial scoping, containment planning, and analyst-ready notes.

2026-07-032

name	pentest-input-protocol-manipulation
description	Input validation and protocol manipulation assessment for injection, parser differential testing, request smuggling, method tampering, header confusion, serialization abuse, and payload mutation. Hands off to authz, business-logic, exploit, or reporting workflows when those become the owner phase.

Input & Protocol Manipulation

Use When

The main question is parser behavior, encoding, method override, header trust, smuggling, serialization, or injection capability.
A request transformation may cross a parser, protocol, or trust boundary.

Handoff Criteria

Hand off to pentest-authentication-authorization-review or pentest-advanced-access-control-auditor when an input anomaly becomes an authorization claim.
Hand off to pentest-business-logic-abuse when the exploitability depends on workflow state.
Hand off to pentest-evidence-structuring-report-synthesis when validation is complete.

Output Schema

Test matrix: vector, payload class, expected secure behavior, observed behavior
Validation state: hypothesis, confirmed, rejected
Minimal reproducible request set

Instructions

Identify the parser or protocol boundary being tested before crafting payloads.
Start with low-noise capability checks, then increase payload complexity only when signal appears.
Compare positive and negative controls for every high-impact claim.
Separate parser anomalies from exploitable security outcomes.
Record exact request transformations required to reproduce behavior.
Escalate to exploit execution only after deterministic primitive confirmation.

Verification Gate

Use structured payload families and deterministic sequencing.
Preserve request/response evidence with context and timing.
Keep tests bounded and reversible by default.
Treat status-code differences as leads until a security effect is proven.
Use positive and negative controls for every high-impact claim.
Cross-check parser behavior with a different content type, method, client, or boundary when ambiguity remains.