Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/shellcode-devInformes y cumplimiento

shellcode-dev

⁨Auth/lab dev: shellcode-format engineering; PIC, ABI, syscalls, encoders, memory permissions, reflective-loader labs, emulator validation.⁩

v2026.11.13-21cd5682 instalaciones+2 en 7 días39 EstrellasMITsincronizado hace 11 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/shellcode-dev

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
YcM4/Tg3av…nRVSA3Cw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete41a0db83…f8628b50
41a0db83572e…cdf2f8628b507 archivos · ⁦15.3 KB⁩
EscaneoMedio2 hallazgos
  • injection.no_confirmationreferences/loader-core-qualification.md:55
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/offensive-coding/shellcode-dev@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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_64 and arm64
  • 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

  1. 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
  2. Pick payload shape

    • Single-stage (small, immediate execution)
    • Two-stage (tiny bootstrap + streamed body)
    • Reflective/in-memory loader path (PE/ELF/Mach-O aware)
  3. Implement ABI-correct stub

    • Preserve required non-volatiles
    • Maintain alignment guarantees
    • Use position-independent data access only
  4. Validate in three layers

    • Static: disassembly and byte checks
    • Emulation: deterministic instruction/memory behavior
    • Runtime: target OS debugger + telemetry sanity
  5. 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, rcx before syscall.
  • If using indirect syscalls, source syscall;ret from a clean ntdll gadget and keep SSN resolution runtime-based.
  • Reflective loading must correctly parse PE exports/imports/relocations and section permissions.

Linux x64/aarch64

  • mmap/mprotect transitions 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 x8 for syscall number and x0-x5 for 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) and offensive-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.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationreferences/loader-core-qualification.md:55
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd56841a0db83Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login