Having a built-in sleep quark would be useful for certain scenarios, such as after adding a cron and simulating enough time for the scheduled task to execute. We can currently do this with execve: ["sleep", "<time>"], but the call already exists, and it'd be nice not to have yet another CLI to sift through

The examples in the READMEs have incorrect quotation characters, which cause execve to treat what should be multiple arguments as a single argument.

It would be nice to be able to provide simple string parameters to the compiled binaries on execution, either in the form of CLI parameters or environment variables. My existing use case is developing a reaction for generic DDoS botnets like Mirai, and providing a fake binary filename on the command line, like so:

Example atom

[
  {
    "name": "EXECUTE-BOT",
    "fork-and-rename": [ "./${1}" ]
  }
]

$ ./reaction x86_64
...
atom: EXECUTE-BOT
        quark: fork-and-rename("./x86_64")

$ ./reaction arm7
...
atom: EXECUTE-BOT
        quark: fork-and-rename("./arm7")

$ ./reaction mips
...
atom: EXECUTE-BOT
        quark: fork-and-rename("./mips")

When executing the created binary, a massive Red Canary banner is output every time, taking up well over half my screen on a large monitor. It would be nice if we could have the option during binary creation to disable this to save screen space on execution.

I am just running the example from README.md and I get this error:

cat reaction.json && cat atoms.json && python3 compose_reaction atoms.json reaction.json test_reaction && ./test_reaction                                                                                      
{                                                                                                                                                                                                                 
    "name": "simple_reaction",                                                                                                                                                                                    
    "atoms": [                                                                                                                                                                                                    
        "HIDDEN-PROCESS-EXEC"                                                                                                                                                                                     
    ]                                                                                                                                                                                                             
}                                                                                                                                                                                                                 
[                                                                                                                                                                                                                 
    {
        "name" : "HIDDEN-PROCESS-EXEC",
        "execve" : [ "mkdir”, “-p", "/tmp/.hidden" ],
        "copy" : [ "/proc/self/exe", "/tmp/.hidden/.chain_reactor_hidden" ],
        "execveat" : [ "/tmp/.hidden/.chain_reactor_hidden", "exit" ],
        "remove" : [ "/tmp/.hidden" ]
    }
]
[...CUT BANNER...]
chain reaction "simple_reaction" 1000 1000
atom: HIDDEN-PROCESS-EXEC
        quark: execve("mkdir”, /tmp/.hidden")
                "mkdir”," one of the dependencies is missing from this system
        failed
chain reaction complete

When I run something such as "id" it properly runs, but mkdir throws a dependency error, which is weird, because I definitely have mkdir on my system:

whereis mkdir
mkdir: /bin/mkdir /usr/share/man/man1/mkdir.1.gz /usr/share/man/man2/mkdir.2.gz

I also tried setting the command as the absolute path (/bin/mkdir) and that didn't work either.
Any idea on why this specific binary wouldn't be working?

Hi
I'm using a straight out of the box Ubuntu build and I get the following when trying to build the illustrative example:

:/code/chain-reactor$ python3 compose_reaction atoms.json reaction.json ./example
Traceback (most recent call last):
File "compose_reaction", line 70, in
assert os.path.exists(os.path.join(script_directory, 'build/_X86_64/chain_reactor')), "You must make chain_reactor first"
AssertionError: You must make chain_reactor first

$ uname -mrs
Linux 5.8.0-55-generic x86_64

$ cat /etc/issue.net
Ubuntu 20.04.2 LTS

$ python3 --version
Python 3.8.5

Request is for the ability to read in and execute Atomic Red Team (ART) YAML/tests in Chain Reactor.

It is likely that a given Atomic Red Team atomic/command does not map 1:1 with the Chain Reactor reaction/atom/quark; however the usability gained from being able to execute a given ART atomic by specifying Technique ID and/or GUID would assist with the usability and automation of using Chain Reactor as a ART execution framework.