Run any Skill in Manus with one click

poc-weaponization

Stars11

Forks1

UpdatedJuly 3, 2026 at 13:05

Safely evaluate, adapt, and rewrite raw public proof-of-concepts into reliable, offline-capable exploits free of backdoors.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AeonDave

AeonDave/malskill

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

File Explorer

2 files

SKILL.md

readonly

name	poc-weaponization
description	Safely evaluate, adapt, and rewrite raw public proof-of-concepts into reliable, offline-capable exploits free of backdoors.

poc-weaponization

When to use

You have a public PoC (from cve-search, GitHub, Exploit-DB, Sploitus, etc.).
The PoC lacks reliability, targets wrong offsets, or was written for Python 2.
You must verify the PoC is not backdoored before running it against a target.

The Weaponization Workflow

1. Safety Audit (Isolated Environment)

Before executing any public exploit script:

Run in an isolated environment first (container or VM with no credentials mounted). A clean-looking PoC may still exfiltrate environment variables or SSH keys at runtime.
Check requirements.txt, setup.py, install.sh, and any package manifest for typosquatted or malicious dependencies and build hooks that execute at install time.
Look for obfuscation: Base64 blocks, eval(), exec(), reversed strings.
Look for callbacks: network connections to third-party hosts outside the intended target (DNS exfiltration, analytics beacons, hardcoded C2).
Check for destructive side-effects: hardcoded rm -rf, DROP TABLE, unnecessary persistence.
Load references/backdoor-patterns.md for the full pattern list.

2. Modernization & Translation

Python 2 → 3: Fix print statements, replace urllib2 with requests, handle bytes/strings encode/decode.
LLM-assisted porting: Using an LLM to translate or adapt PoC code is acceptable; review output for hallucinated API calls or function signatures that do not exist in the target library version.
Shellcode: Strip hardcoded shellcode; replace with parameterized payload injection (e.g., msfvenom-generated blob via --payload flag).

3. Reliability & Generalization

Hardcoded constraints: Eliminate hardcoded IPs, ports, and offsets. Implement argparse or click to allow parameterized inputs (--target, --port, --lhost, --lport).
Error handling: Avoid raw stack traces on network timeouts. Handle ConnectionRefusedError, HTTP 404s, and unexpected payload formats cleanly.
Verification mode: Add a --check flag that securely tests if the vulnerability is present without actually firing the payload or dropping the shell.

References

references/backdoor-patterns.md — Common backdoor and beacon patterns in poisoned PoCs; load during step 1.

More from this repository

same repository

mcpwn

AeonDave/malskill

Drive the MCPwn Kali-backed MCP server cleanly and fast: create a session, discover tools via the catalog (list_catalog/get_tools/get_tool/run_tool) instead of guessing names, pick the right execution path (execute_command vs detach+poll_job vs interactive shell), move files with the correct mechanism (write_workspace_file, request_upload/request_download data plane, import_artifact_to_workspace, upload_to_target, list_payloads/get_payload), and bring up connectivity (tunnel_up VPN/proxy/forward, tunnel_revshell, penelope reverse shells, run_in_shell/stabilize_shell). Use whenever running MCPwn / mcpwn_* tools, a Kali MCP, or when a run stalls on timeouts, lost output, missing routes, wrong tool names, or clumsy file transfer.

2026-07-1911

reading-budget-discipline

AeonDave/malskill

Keep the context window lean when reading large data. Use before opening big files, logs, dumps, PCAPs, decompiler output, research corpora, or a folder of worker artifacts. Enforces grep-first + windowed reads, extract-don't-hoard, and context quarantine (delegate a huge read to a sub-agent that returns a digest).

2026-07-1911

web-exploit-technique

AeonDave/malskill

Auth assessment: web impact-validation; SQLi, SSTI, XXE, command injection, SSRF, XSS, uploads, deserialization, smuggling, WAF/parser checks.

2026-07-1911

1337

AeonDave/malskill

Mode: /1337 - structured operator behaviour for coding and security; forces explicit reasoning, fast decisions, todos/lists, exact terms, evidence, verification, safety override.

2026-07-1611

pwn-ctf

AeonDave/malskill

Lab/CTF: pwn/binary challenges; native binaries, memory corruption, format strings, heap/ROP/SROP, shellcode artifacts, seccomp, kernel labs.

2026-07-1611

reversing-technique

AeonDave/malskill

Auth/lab: reverse engineering methodology; malware triage, patch diffing, firmware/protocol RE, protections, exploitability handoff evidence.

2026-07-1611

poc-weaponization

When to use

You have a public PoC (from cve-search, GitHub, Exploit-DB, Sploitus, etc.).

The PoC lacks reliability, targets wrong offsets, or was written for Python 2.

You must verify the PoC is not backdoored before running it against a target.

The Weaponization Workflow

1. Safety Audit (Isolated Environment)

Before executing any public exploit script:

Run in an isolated environment first (container or VM with no credentials mounted). A clean-looking PoC may still exfiltrate environment variables or SSH keys at runtime.

Check requirements.txt, setup.py, install.sh, and any package manifest for typosquatted or malicious dependencies and build hooks that execute at install time.

Look for obfuscation: Base64 blocks, eval(), exec(), reversed strings.

Look for callbacks: network connections to third-party hosts outside the intended target (DNS exfiltration, analytics beacons, hardcoded C2).

Check for destructive side-effects: hardcoded rm -rf, DROP TABLE, unnecessary persistence.

Load references/backdoor-patterns.md for the full pattern list.

2. Modernization & Translation

Python 2 → 3: Fix print statements, replace urllib2 with requests, handle bytes/strings encode/decode.

LLM-assisted porting: Using an LLM to translate or adapt PoC code is acceptable; review output for hallucinated API calls or function signatures that do not exist in the target library version.

Shellcode: Strip hardcoded shellcode; replace with parameterized payload injection (e.g., msfvenom-generated blob via --payload flag).

3. Reliability & Generalization

Hardcoded constraints: Eliminate hardcoded IPs, ports, and offsets. Implement argparse or click to allow parameterized inputs (--target, --port, --lhost, --lport).

Error handling: Avoid raw stack traces on network timeouts. Handle ConnectionRefusedError, HTTP 404s, and unexpected payload formats cleanly.

Verification mode: Add a --check flag that securely tests if the vulnerability is present without actually firing the payload or dropping the shell.

References

references/backdoor-patterns.md — Common backdoor and beacon patterns in poisoned PoCs; load during step 1.