GH Module Null v2 0 UserGuide
GH Module Null v2 0 UserGuide
1OVERVIEW............................................................................................3
2INSTALLATION......................................................................................3
2.1CONFIGURATION..................................................................................................... 3
3PAYLOAD EXECUTION............................................................................3
3.1RUN ONCE............................................................................................................ 3
4FOOTPRINT..........................................................................................3
5RECEIPT XML FORMAT...........................................................................3
5.1XML EXAMPLE...................................................................................................... 3
5.2FIELD DEFINITIONS................................................................................................. 4
CL BY: 2355679
CL REASON: Section
1.5(c),(e)
DECL ON: 20370522
DRV FRM: COL 6-03
SECRET//ORCON//NOFORN
SECRET//ORCON//NOFORN
2
SECRET//ORCON//NOFORN
SECRET//ORCON//NOFORN
1 Overview
NULL is a module that lays down and executes a payload. When a payload is
chosento use this module, NULL will drop the payload to disk, execute it, and exit
immediately. Note that the payload is not deleted.
As of version 2.0, NULL can optionally also lay down (but not execute) an arbitrary
number of other user provided files.
This module is meant to be used with either one-shot tools (e.g., a survey tool) or
with payloads that provide their own persistence separate from Grasshopper,
allowing existing tools to make use of the Grasshopper Rule Engine and payload
obfuscation.
NULL supports 32- and 64-bit EXE payloads only.
2 Installation
NULL will deploy and execute an EXE payload at a user-specified location on the
target filesystem. NULL does not provide any soft persistence, nor will it delete the
payload after execution.
2.1 Configuration
The following fields are configured at build time to specify NULL's installation
behavior.
Defaul Description
Field
t
Payload Path None Path to Payload EXE on target started by NULL
If the path does not exist, it is created.
Additional Files None Local and remote paths for any desired additional files.
3 Payload Execution
The payload is executed once as a normal process at the privilege level of the
Grasshopper process. All additional files are dropped before the payload is dropped.
If any file is not able to be dropped for any reason, all dropped files will be securely
deleted and the payload will not be executed.
The NULL module does not need to uninstall; it does not leave any stubs and does
notprovide any persistence. The payload is responsible for removing itself from the
target.
3
SECRET//ORCON//NOFORN
SECRET//ORCON//NOFORN
4 Footprint
The NULL module writes an unobfuscatedpayload to the target filesystem. The path
is specified by the user at build time. This file will not be deleted by Grasshopper.
The process of the payload executable is visible in the Task Manager during
execution.
Appendix A:
4
SECRET//ORCON//NOFORN
SECRET//ORCON//NOFORN
5
SECRET//ORCON//NOFORN