offensive-basic-exploitation
Week 5 exploit development curriculum. Foundational exploitation techniques: controlling EIP/RIP, ROP chain construction, ret2libc, shellcode injection, heap spraying, bypass techniques for ASLR/NX/stack canaries. Use when building initial PoCs or understanding classic exploitation primitives.
Install / Use
npx skills add SnailSploit/Claude-Red --skill offensive-basic-exploitationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of offensive-basic-exploitation
offensive-basic-exploitation scores 87/100 on our quality scale, 677th of 1,108 Security skills we index.
Its SKILL.md is 336 KB long, well organised into 776 sections with 243 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.
With 6,850 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so offensive-basic-exploitation is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the first 100 KB of the file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
offensive-basic-exploitation compared with similar skills
All 4 of these similar skills score higher than offensive-basic-exploitation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| offensive-basic-exploitation (this skill)by SnailSploit | 87 | 6.8k | 58d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install offensive-basic-exploitation?
- Run
npx skills add SnailSploit/Claude-Red --skill offensive-basic-exploitation. The install tabs above show the steps for each supported agent. - Which AI agents does offensive-basic-exploitation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is offensive-basic-exploitation safe to use?
- Our scan of the first 100 KB of the file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is offensive-basic-exploitation still maintained?
- The repository was last updated about 2 months ago, so offensive-basic-exploitation is actively maintained.
Skill content
View source on GitHubSKILL: Week 5: Basic Exploitation (Linux with Mitigations Disabled)
Metadata
- Skill Name: basic-exploitation
- Folder: offensive-basic-exploitation
- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/5-basic-exploitation.md
Description
Week 5 exploit development curriculum. Foundational exploitation techniques: controlling EIP/RIP, ROP chain construction, ret2libc, shellcode injection, heap spraying, bypass techniques for ASLR/NX/stack canaries. Use when building initial PoCs or understanding classic exploitation primitives.
Trigger Phrases
Use this skill when the conversation involves any of:
basic exploitation, EIP control, RIP control, ROP chain, ret2libc, shellcode injection, heap spray, ASLR bypass, NX bypass, stack canary bypass, week 5
Instructions for Claude
When this skill is active:
- Load and apply the full methodology below as your operational checklist
- Follow steps in order unless the user specifies otherwise
- For each technique, consider applicability to the current target/context
- Track which checklist items have been completed
- Suggest next steps based on findings
Full Methodology
Week 5: Basic Exploitation (Linux with Mitigations Disabled)
Overview
created by AnotherOne from @Pwn3rzs Telegram channel.
Now that you can find and analyze vulnerabilities (Week 2 & 4), it's time to learn exploitation. This week focuses on fundamental exploitation techniques in a simplified Linux environment with modern mitigations (DEP, ASLR, stack canaries) disabled. Mastering these basics is essential before tackling mitigation bypasses in Week 7.
Next week (Week 6) we'll focus on understanding mitigations in both Linux and Windows. Week 7 will cover bypassing them.
Learning Environment:
- CPU arch (default): amd64 (x86-64)
- OS: Ubuntu 24.04 LTS (Linux)
- Compiler Flags: Disable protections (
-fno-stack-protector,-no-pie,-z execstackfor ret2shellcode labs,/GS-) - ASLR: Keep enabled system-wide; disable per-process (
setarch -R) or in GDB (set disable-randomization on) for deterministic labs - Focus: Pure exploitation techniques without bypass complexity
Day 1: Environment Setup and Stack Overflow Fundamentals
- Goal: Set up exploitation lab and understand stack buffer overflow mechanics.
- Activities:
- Reading:
- "Hacking: The Art of Exploitation" 2nd edition, by Jon Erickson - Chapter 0x300: "EXPLOITATION"
- Smashing The Stack For Fun And Profit - Classic paper
- Online Resources:
- Tool Setup:
- Ubuntu VM with protections disabled
- pwntools, pwndbg, ROPgadget
- Exercise:
- Compile and exploit first vulnerable program
- Overwrite return address to execute shellcode
- Reading:
Context: QNAP Stack Overflow (CVE-2024-27130)
- Recall the QNAP QTS Stack Overflow from Week 1? That was a classic stack buffer overflow caused by
strcpywithout bounds checking—exactly what we'll be exploiting today. - While modern systems have mitigations (which we'll disable for now), the underlying mechanic remains the same: overwriting the return address to hijack control flow.
Deliverables
- Environment:
~/check_env.shpasses and you recorded its output - Binary:
vuln1built and verified withchecksec - Primitive proof: RIP control demonstrated (controlled crash address)
- Exploit:
exploit1.py(or equivalent) spawns a shell reliably - Notes: brief writeup covering offset, return target, and payload layout
Setting Up the Lab Environment
Ubuntu VM Configuration:
[!IMPORTANT] ASLR Policy: Keep ASLR enabled system-wide for security. Disable only per-process for labs. Never disable ASLR globally on a machine connected to the internet.
# ============================================================
# ASLR CONFIGURATION (Per-Process Only - Do NOT disable globally!)
# ============================================================
# Option 0: Disable ASLR system-wide
# echo 0 | sudo tee /proc/sys/kernel/randomize_va_space
# echo "kernel.randomize_va_space = 0" | sudo tee /etc/sysctl.d/99-disable-aslr.conf
# sudo sysctl --system
# Option 1: Disable in GDB (recommended for debugging)
# In GDB/pwndbg:
# (gdb) set disable-randomization on # Default in GDB
# (gdb) set disable-randomization off # If you want ASLR during debug
# Option 2: Disable for a single binary run
setarch x86_64 -R ./binary
# Option 3: In pwntools (for local process only)
# p = process('./binary', aslr=False)
# VERIFY: Check system ASLR is STILL ENABLED
cat /proc/sys/kernel/randomize_va_space
# Should output: 2 (full ASLR) - DO NOT change this!
# If you previously disabled ASLR system-wide, RE-ENABLE it:
# echo 2 | sudo tee /proc/sys/kernel/randomize_va_space
# sudo rm -f /etc/sysctl.d/99-disable-aslr.conf # Remove any persistent config
# ============================================================
# INSTALL ESSENTIAL TOOLS
# ============================================================
sudo apt update
sudo apt install -y \
nasm \
strace \
ltrace \
ruby \
ruby-dev \
libc6-dbg \
checksec \
patchelf
cd ~/crash_analysis_lab
source .venv/bin/activate
pip install ropgadget
# Install one_gadget (quick shell gadgets)
sudo gem install one_gadget
# Install radare2 (optional but useful)
cd ~/tools
git clone --depth 1 --branch master https://github.com/radareorg/radare2
cd radare2
sys/install.sh
# Check glibc version (important for heap exploitation)
ldd --version
# Ubuntu 24.04 ships with glibc 2.39
# ============================================================
# STANDARDIZED COMPILATION PROFILES (AMD64)
# ============================================================
# Create a Makefile with canonical build profiles for labs:
cat > ~/lab-Makefile << 'MAKEFILE'
# Lab Exploitation Makefile - AMD64 Only
# Usage: make <target> BINARY=myprogram SOURCE=myprogram.c
CC = gcc
SOURCE ?= vuln.c
BINARY ?= vuln
# Base flags for all builds (AMD64)
BASE_CFLAGS = -g -O0 -fno-omit-frame-pointer -fno-stack-protector
BASE_LDFLAGS = -no-pie
# Training profiles:
# 0. disabled: most things disabled
# 1. training-shellcode: NX disabled, for ret2shellcode exercises
# 2. training-rop: NX enabled, for ROP/ret2libc exercises
# 3. training-relro-off: Partial RELRO, for GOT overwrite exercises
# 4. training-full-relro: Full RELRO, to demonstrate GOT write fails
# 5. format-sec: for format-security bugs
disabled: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -w -fcf-protection=none -z execstack -o $(BINARY) $(SOURCE)
@echo "Built: NX=OFF, Canary=OFF, PIE=OFF, RELRO=Partial"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
training-shellcode: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -z execstack -o $(BINARY) $(SOURCE)
@echo "Built: NX=OFF, Canary=OFF, PIE=OFF, RELRO=Partial"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
training-rop: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -o $(BINARY) $(SOURCE)
@echo "Built: NX=ON, Canary=OFF, PIE=OFF, RELRO=Partial"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
training-relro-off: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -fcf-protection=none -Wl,-z,norelro -o $(BINARY) $(SOURCE)
@echo "Built: NX=ON, Canary=OFF, PIE=OFF, RELRO=OFF"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
training-full-relro: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -fcf-protection=none -Wl,-z,relro,-z,now -o $(BINARY) $(SOURCE)
@echo "Built: NX=ON, Canary=OFF, PIE=OFF, RELRO=FULL (GOT read-only!)"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
format-sec: $(SOURCE)
$(CC) $(BASE_CFLAGS) $(BASE_LDFLAGS) -w -fcf-protection=none -Wno-format-security -o $(BINARY) $(SOURCE)
@echo "Built: NX=OFF, Canary=OFF, PIE=OFF, RELRO=Partial"
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
# Show all protections
check:
@checksec --file=$(BINARY) 2>/dev/null || pwn checksec $(BINARY)
clean:
rm -f $(BINARY) *.o
.PHONY: disabled training-shellcode training-rop training-relro-off training-full-relro format-sec check clean
MAKEFILE
echo "Makefile created at ~/lab-Makefile"
echo "Copy to your lab directory: cp ~/lab-Makefile ./Makefile"
[!NOTE] Ubuntu 24.04:
- Uses glibc 2.39 with full safe-linking and removed hooks
- Requires
python3-venvfor pip package installation (PEP 668)- For classic heap techniques, consider using Docker with older Ubuntu
GDB Enhancement Options
Verify Setup:
mkdir -p exploit
cd exploit
cp ~/lab-Makefile ./Makefile
source ~/crash_analysis_lab/.venv/bin/activate
# Test pwntools
python3 -c "from pwn import *; print('pwntools OK')"
# Test compilation without protections (AMD64)
cat > test.c << 'EOF'
#include <stdio.h>
#include <string.h>
int main() {
char buf[100];
gets(buf); // Vulnerable: reads from stdin, no bounds check
return 0;
}
EOF
make training-shellcode BINARY=test SOURCE=test.c
#gcc -g -O0 -w -fno-stack-protector -z execstack -no-pie test.c -o test
# Should compile without errors (-w suppresses gets() warning)
# Check binary protections (should all be disabled)
# Use either: checksec (from apt) or pwn checksec (from pwntools)
# checksec --file=./test
# Or: pwn checksec ./test
# Expected output (may vary slightly by checksec version):
# Arch: amd64-64-little
# RELRO: Partial RELRO
# Stack: No canary found
# NX: NX unknown - GNU_STACK missing (effectively disabled via -z execstack)
# PIE: No PIE (0x400000)
# Stack: Executable
# RWX: Has RWX segments
# SHSTK: Enabled (Intel CET Shadow Stack - CPU feature, not binary)
# IBT: Enabled (Intel CET Indirect Branch Tracking)
# Note: "NX unknown" with "Stack: Executable" means shellcode execution works
# ============================================================
# SANITY CHECK SCRIPT (Run Before Each Lab)
# ============================================================
cat > ~/check_env.sh << 'SCRIPT'
#!/bin/bash
# Lab Environment Sanity Check
# Run: ./check_env.sh [binary]
echo "=== Lab Environment Check ==="
echo ""
# System info
echo "[*] System Information:"
echo " Kernel: $(uname -r)"
echo " glibc: $(ldd --version | head -1 | awk '{print $NF}')"
echo ""
# ASLR status
echo "[*] ASLR Status:"
ASLR=$(cat /proc/sys/kernel/randomize_va_space)
case $ASLR in
0) echo " WARNING: ASLR is DISABLED system-wide (insecure!)" ;;
1) echo " Partial ASLR (stack only)" ;;
2) echo " Full ASLR enabled (correct for system)" ;;
esac
echo ""
# Binary check
if [ -n "$1" ] && [ -f "$1" ]; then
echo "[*] Binary Analysis: $1"
echo " Architecture: $(file "$1" | grep -oE '(32|64)-bit')"
checksec --file="$1" 2>/dev/null || pwn checksec "$1" 2>/dev/null
echo ""
fi
# GDB randomization
echo "[*] GDB ASLR (check inside GDB with 'show disable-randomization'):"
echo " Default: ON (disabled randomization = deterministic addresses)"
echo ""
echo "[+] Environment check complete."
echo " For per-process ASLR disable: setarch x86_64 -R ./binary"
echo " Or in pwntools: process('./binary', aslr=False)"
SCRIPT
chmod +x ~/check_env.sh
echo "Sanity check script created: ~/check_env.sh"
~/check_env.sh
pwntools Essentials
Before diving into exploitation, master these pwntools fundamentals. The ELF() class is your primary interface for analyzing binaries—use it throughout this course.
ELF() Basics:
cd ~/exploit
source ~/crash_analysis_lab/.venv/bin/activate
cp ~/crash_analysis_lab/vuln_no_protect .
#!/usr/bin/env python3
# ~/exploit/1.
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
