CyberKit

String Stacking

Also called Stack strings.

Building strings byte by byte at runtime to hide them from triage.

What it is

A technique where a program constructs strings on the stack one character at a time, or decodes them in place, instead of storing them as readable literals. The strings never exist statically in the file.

Why it matters

Stack strings defeat simple strings extraction, hiding URLs, paths, and commands until the code runs. Their presence is itself a sign of deliberate evasion and points analysts toward dynamic recovery.

In practice

A loader that assembles its C2 hostname character by character on the stack, invisible to a static strings dump.

What to look for

  • Characters moved onto the stack one at a time.
  • Few readable strings in static analysis.
  • Strings that appear only in memory at runtime.

Common mistake

Assuming no strings means no capability. Run it or emulate it to see what gets built.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Ghidra Open source

    A disassembler and decompiler for reading what a sample's code actually does. Our notes.

  • YARA Open source

    Writes rules that match a family's code or strings across many files. Our notes.

  • VirusTotal Commercial

    Shows how many engines flag a file, plus its relations to domains and other samples.

  • ANY.RUN Commercial

    An interactive sandbox where you watch a sample run and click through what it asks for.

Read next

Sources