ARTist module for the Gunshop challenge in the ASIS CTF 2018 Finals
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

ASIS CTF 2018 Finals - Gunshop Module


This module is built for the Gunshop Challenge in the ASIS CTF 2018 Finals. It leaks the AES key, redirects https to a proxy running on 'proxy:8080', disables certificate checks and bypasses custom certificate pinning.

You can find more information in the Challenge Write-Up


Assuming you have already installed the Module SDK, you can build this project by simply invoking make on a commandline from within the project's root directory. It will create a zip file in the out folder that can be pushed to the device and imported via the ArtistGui module management.


The module consist of two parts: The codelib that contains additional helper functions and the optimization passes for the ARTist compiler that inject e.g. calls to codelib methods.

While the code for the instrumentation passes can be found in the src folder, the codelib part resides in a second repository here and the resulting apk is (for now) committed as a part of this repository to be able to immediately build it after checkout.

ARTist - The Android Runtime Instrumentation and Security Toolkit

ARTist is a flexible open source instrumentation framework for Android's apps and Java middleware. It is based on the Android Runtime’s (ART) compiler and modifies code during on-device compilation. In contrast to existing instrumentation frameworks, it preserves the application's original signature and operates on the instruction level.

ARTist can be deployed in two different ways: First, as a regular application using our ArtistGui project that allows for non-invasive app instrumentation on rooted devices, or second, as a system compiler for custom ROMs where it can additionally instrument the system server (Package Manager Service, Activity Manager Service, ...) and the Android framework classes (boot.oat). It supports Android versions after (and including) Marshmallow 6.0.

For detailed tutorials and more in-depth information on the ARTist ecosystem, have a look at our official documentation and join our Gitter chat.

Current state: Beta

We recently entered the beta phase for Project ARTist and hence not everything will work perfectly out-of-the-box, yet. However, with the new documentation and module SDK, it is easier than ever to get involved and, e.g., write own modules. To keep up with the current progress, keep an eye on the GitHub repositories of ARTist, check for new blog posts at and feel free to leave feedback in our Gitter chat.


We hope to create an active community of developers, researchers and users around Project ARTist and hence are happy about contributions and feedback of any kind. There are plenty of ways to get involved and help the project, such as testing and writing Modules, providing feedback on which functionality is key or missing, reporting bugs and other issues, or in general talk about your experiences. The team is actively monitoring Gitter and of course the repositories, and we are happy to get in touch and discuss. We do not have a full-fledged contribution guide, yet, but it will follow soon (see beta announcement above).


ARTist is based on a paper called ARTist - The Android Runtime Instrumentation and Security Toolkit, published at the 2nd IEEE European Symposium on Security and Privacy (EuroS&P'17). The full paper is available here. If you are citing ARTist in your research, please use the following bibliography entry:

  title={ARTist: The Android runtime instrumentation and security toolkit},
  author={Backes, Michael and Bugiel, Sven and Schranz, Oliver and von Styp-Rekowsky, Philipp and Weisgerber, Sebastian},
  booktitle={2017 IEEE European Symposium on Security and Privacy (EuroS\&P)},

There is a follow-up paper where we utilized ARTist to cut out advertisement libraries from third-party applications, move the library to a dedicated app (own security principal) and reconnect both using a custom Binder IPC protocol, all while preserving visual fidelity by displaying the remote advertisements as floating views on top of the now ad-cleaned application. The full paper The ART of App Compartmentalization: Compiler-based Library Privilege Separation on Stock Android, as it was published at the 2017 ACM SIGSAC Conference on Computer and Communications Security (CCS'17), is available here.