offensive-techniques/social-engineering-technique/SKILL.md
Social engineering methodology for authorized red team engagements: pretext development, phishing campaign design, vishing, physical social engineering, target research, and security awareness metrics. Use when planning social engineering campaigns, designing pretexts, or assessing human-factor security controls during authorized engagements.
npx skillsauth add aeondave/malskill social-engineering-techniqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Goal: assess organizational resilience to human-factor attacks through authorized, controlled social engineering campaigns.
phishing-technique (GoPhish, Evilginx2, domain setup).osint-technique.offensive-coding/shellcode-dev/, offensive-tools/exploits/metasploit/.Before any social engineering activity:
Before preparing a campaign, classify the human objective and the safest authorized channel for testing it.
osint-technique and passive research first for target context, move to phishing-technique only when the scenario actually requires email or AitM infrastructure, and keep payload/delivery tools as a later support layer.Common trigger categories:
See phishing-technique for infrastructure setup. Key methodology decisions:
| Metric | Description | Industry baseline | |--------|-------------|-------------------| | Open rate | Recipients who opened | 30-50% | | Click rate | Recipients who clicked | 10-25% | | Credential submission | Recipients who entered creds | 5-15% | | Payload execution | Recipients who ran attachment | 3-10% | | Reporting rate | Reported to security | 5-15% (target >30%) | | Time to first click | Elapsed from send to first click | Typically <5 min |
references/pretext-library.md — categorized pretext templates for phishing, vishing, and physical scenarios.references/campaign-planning.md — campaign design worksheet and metrics tracking template.data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.