offensive-tools/evasion/shellcode-fluctuation/SKILL.md
C++ shellcode fluctuation technique that encrypts injected shellcode between C2 sleep intervals to evade EDR memory scans. Use when implants are being detected by memory-scanning EDR products during sleep.
npx skillsauth add aeondave/malskill shellcode-fluctuationInstall 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.
C++ in-memory evasion — XOR-encrypts shellcode in RX pages during C2 sleep to defeat memory scanners.
# Clone and build with MSVC
git clone https://github.com/mgeeky/ShellcodeFluctuation
# Open in Visual Studio, build Release x64
# Or MinGW
x86_64-w64-mingw32-g++ -O2 -o fluctuator.exe main.cpp -lntdll
[Shellcode in memory]
Awake: → Decrypt → Execute → Sleep
Asleep: → Encrypt (XOR) → change PROT to RW → Scanner sees garbage
Wake: → change PROT to RX → Decrypt → Resume
#define SHELLCODE_FLUCTUATE true
#define XOR_KEY 0xdeadbeef
#define SLEEP_INTERVAL_MS 5000
Integrate into Cobalt Strike BOF loader:
FluctuateShellcode() wrapper before Sleep()Combine with indirect syscalls:
// Replace VirtualProtect with direct NtProtectVirtualMemory
// via syscall stub to avoid API hooks
| File | When to load |
|------|--------------|
| references/ | Hook evasion and memory protection patterns |
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.