CHIMERA

(Corpora Heterogenization by Invocation Modulation for Elfs in Reversing Analyses)

I curated these GitHub projects and created these scripts to generate fairly large corpora of binaries. Part of corpus size is the size of the curated collection which at it's largest, CHIMERA had a source corpus of 40-50 GitHub projects, however, I never got all of these submoduled in this repo. Since I actively developed CHIMERA, Vagrant and containers have been developed tremendously and grew in popularity (and I have become aware of them!) I think they'd be great alternatives to hosting CHIMERA as exclusively as a repo.

Overview of my usage of CHIMERA for ByteWise

Source to binary corpora creation based on multiple different compiler invocations, for say creating a corpora of binaries with every different optimization level. Currently you can customize invocations.cfg with compiler, cflags, extension for the binaries, and folder for the binaries. This allows for exercising compile-time obfuscators like o-llvm to create corpora of binaries that exhibit different levels and types of obfuscation transformations. These corpora could be used to test automated reverse engineering analyses or for other research. o-llvm is confirmed to work with Chimera.

Chimera is simple set of bash scripts and a C corpora with build processes that have been standardized by a buildit.chimera script.

Additions to the source corpus as well as additions to the mechanics of Chimera are welcome.

Vision

The vision for Chimera is to be an automatic corpora generation tool that can handle source-to-source, compile-time obfuscators and binary rewriters, whether they are command-line or GUI. We hope also to add theZoo malware sources as part of the Chimera source corpora to make it much more relevant for malware analyses.

Requirements

Many things:

• Bash
• Make
• Autoconf
• Configure
• Automake
• CMake

But also every dependency for each source project. This is an ongoing issue. We may release Chimera as a virtual machine appliance once work is more mature.

Using Chimera

./chimera.sh example.invocations.cfg sources.cfg This will run every compiler invocation in "example.invocation.cfg" for every "buildit.chimera" script listed in "sources.cfg"

"example.inovcations.cfg" should be composed of lines in the form: compiler_path cflags binary_extension build_folder "sources.cfg" should be composed of one path to a "buildit.chimera" per line