Skip to main content
Mythic 4.0 replaces wrapper payload type allowlists with metadata-driven compatibility. A normal payload builder reports what it produced; a wrapper declares the exact OS, architecture, and format combinations it accepts.

Report build metadata

Mythic records the selected OS. The builder returns the resulting architecture and file format.
Common architecture values are x86, x64, arm, and arm64. Common formats are exe, dll, shellcode, macho, elf, so, and dylib.

Declare wrapper requirements

Multiple requirement rules are ORed. Every field in one requires object must match. payload_type is optional; omit it when any payload type with the required file metadata is acceptable. Optional when conditions bind a rule to the wrapper’s own build parameter values. You can think of this like: When my build parameter’s are configured like X, I require that the payload I’m trying to wrap have this configuration.
The resulting sync JSON is: