shellcode-dev
Auth/lab dev: shellcode-format engineering; PIC, ABI, syscalls, encoders, memory permissions, reflective-loader labs, emulator validation.
v2026.11.13-21cd5682 installazioni+2 in 7 giorni39 StelleMITsincronizzato 11 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/shellcode-devScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto41a0db83…f8628b50
41a0db83572e…cdf2f8628b507 file · 15.3 KBScansioneMedio2 segnalazioni
- injection.no_confirmationreferences/loader-core-qualification.md:55
- Link a domini esterni
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-coding/shellcode-dev@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Build shellcode as a constrained engineering problem: small PIC code, strict ABI behavior, reliable memory transitions, and reproducible test loops.
This skill is for implementation and validation workflow. It is not a vulnerability discovery skill.
When to activate
- Writing or reviewing shellcode/stagers in ASM/C/Python pipelines
- Building cross-platform syscall-based payloads (Windows/Linux/macOS)
- Porting payloads between
x86_64andarm64 - Handling bad-byte restrictions with encoder/decoder stages
- Implementing reflective/manual in-memory loading workflows
- Debugging crashes caused by calling-convention or stack-alignment mistakes
- Verifying payload behavior with emulator/disassembler tooling before runtime tests
If the task is specifically about BOFs, prefer offensive-coding/bof-dev first. If it is specifically about stack masquerade or syscall gates, combine with offensive-coding/stack-spoofing-dev or offensive-coding/indirect-syscall-dev.
Core workflow
Define execution contract first
- Target OS + architecture + entry assumptions
- Available registers, expected stack alignment, bad-byte set, max size
- Whether network/file APIs are allowed or syscall-only is required
Pick payload shape
- Single-stage (small, immediate execution)
- Two-stage (tiny bootstrap + streamed body)
- Reflective/in-memory loader path (PE/ELF/Mach-O aware)
Implement ABI-correct stub
- Preserve required non-volatiles
- Maintain alignment guarantees
- Use position-independent data access only
Validate in three layers
- Static: disassembly and byte checks
- Emulation: deterministic instruction/memory behavior
- Runtime: target OS debugger + telemetry sanity
Harden incrementally
- Add only required obfuscation/encoding
- Re-test after each hardening change
- Keep a plain debug build to avoid blind debugging
Platform rules that break payloads most often
Windows x64
- Respect Microsoft x64 ABI and shadow space requirements.
- Syscall path expects
mov r10, rcxbeforesyscall. - If using indirect syscalls, source
syscall;retfrom a cleanntdllgadget and keep SSN resolution runtime-based. - Reflective loading must correctly parse PE exports/imports/relocations and section permissions.
Linux x64/aarch64
mmap/mprotecttransitions are part of payload lifecycle; test all return paths.- For x64 syscalls, syscall number/arg placement must match kernel ABI (
rax+rdi/rsi/rdx/r10/r8/r9). - For aarch64 syscalls, use
x8for syscall number andx0-x5for args. - Avoid assuming vDSO location or fixed helper addresses.
macOS x64/arm64
Apple's macOS release notes identify Tahoe 26 as the last major release supporting Intel Macs. Apple's 26.3 security notes list the fix for CVE-2026-20627. These are platform lifecycle and security-update facts, not qualification of the workflows in this skill.
- Syscall tables and calling details differ from Linux; validate against XNU sources/current targets.
- Treat Mach-O and dyld assumptions as version-sensitive.
- arm64 stack alignment and calling convention errors fail fast; emulate and runtime-test both.
Encoder and polymorphism guidance
- Use encoding to satisfy transport/bad-byte constraints, not as a default.
- Keep decoder stubs minimal and architecture-appropriate.
- Polymorphism/metamorphism increases implementation risk and detection surface if overused.
- Prefer deterministic transforms you can regression-test over “clever” mutation logic.
- Map evasion assumptions to ATT&CK-style behavior expectations and verify with runtime telemetry.
Python/C integration pattern
- Use Python (pwntools/Keystone/Capstone/Unicorn) for generation, assembly, disassembly, and emulation harnesses.
- Use C/C++ (or Rust/Go) wrappers for runtime loaders/injectors and platform APIs.
- Keep shellcode bytes and loader logic separable so you can swap payload versions quickly.
- Always retain one end-to-end harness that runs:
generate -> inspect -> emulate -> execute test.
Quality gates before shipping
- Byte-level constraints pass (
badchars, size, null/newline policy) - Stack/register invariants verified at entry/exit
- Memory permissions transitions are reversible and error-checked
- No hardcoded OS-build-specific syscall numbers unless explicitly pinned for research
- At least one emulator run and one real runtime debug pass on target architecture
- Crash artifacts and logs are reproducible with the same payload bytes
Resources
- references/platform-workflows.md — concrete Windows/Linux/macOS build and validation flows, including syscall and memory-transition checkpoints
- references/tooling-and-labs.md — practical usage of pwntools, Capstone, Keystone, Unicorn, debugger loops, and test harness patterns
- references/encoders-and-stagers.md — staged payload patterns, bad-byte encoders, polymorphism trade-offs, and failure modes
- references/payload-protection-and-shaping.md — payload key splitting over ambient state, MBA-obfuscated key material, encrypted container layout, and binary shaping vs static/ML classifiers; load when building or reviewing a loader's payload-protection pipeline
- references/evasion-patterns-from-projects.md — transferable shellcode-dev engineering patterns from real implementations (runtime SSN mapping, recycled syscall gates, DESYNC readiness checks, sleep masking pipelines, CFG-aware gadget handling)
- references/loader-core-qualification.md — load when qualifying, porting, or reviewing a raw PIC loader core (extracted
.text/.rdata) or its wrapper: defect taxonomy (thunk-slot placement, SSE/section alignment, decode-cursor vs ABI conflation, kernel-dependent paths), crash-signature triage on Windows, and the per-backend gate recipe - Upstream methodology:
offensive-techniques/binary-exploitation-technique(where shellcode fits in the chain) andoffensive-ctf/pwn-ctf/references/shellcode-filtering.md(byte-blacklist recipes). - Start with
references/platform-workflows.md; wrong platform assumptions break payloads faster than bad-byte or evasion mistakes.
File di questa versione
references/629.5 KB
- encoders-and-stagers.md2.0 KB
- evasion-patterns-from-projects.md8.1 KB
- loader-core-qualification.md6.5 KB
- payload-protection-and-shaping.md6.3 KB
- platform-workflows.md4.0 KB
- tooling-and-labs.md2.6 KB
- SKILL.md7.0 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaPrompt injection · injection.no_confirmationreferences/loader-core-qualification.md:55
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 41a0db83 | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in Report e compliance
Vai alla categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login