Having problems with hikari not compiling or Linux? Don’t want to waste your time pouring in hours for defeat? Hikari too outdated? Don’t worry, for an idiot (me) has gone through that just to make it public for you!
-> Hikari from Zangh is an old toy llvm based obfuscator.
-> This works cross-platform, but targets mainly ios and macOS.
-> You can uss this for linux and windows too!
-> It's a pain to set up though, which is why alot of people get deterred.
-> it took me 11 hours for a single build even with past experience. I bet it takes less than half an hour on a mac, but.... linux supremacy
-> It's a pain to get ios/macos stuff to get working on linux, but people manage i guess if you're determined enough.
-> Releases
(They might be compressed over and over, so it'll take a while to deflate. mine is over a giga-byte...)
-> LLVM18.1+
-> LLVM19.1+
-> LLVM 20.1+
-> You can use them with theos
-> on your host machine too! just set ‘‘ld‘‘ to your linux's linker (you get this by running:)
which ld
-> It may be tricky to get this working on host machine, especially newer clang builds. old ones with c++17 should work fine like 18.
-> you'll need to make a huge command and include some theos headers too (you can enable verbosity in theos with MESSAGES=yes flag, and use that to figure out correct command.
You're going to have to follow each of these steps. It's not hard to do it properly if you listen.
- Download it from releases and unzip it, until you reach a
my-toolchainnamed folder or similar. - Download an old IOS sdk (example 13.7) from theos/sdks
- Move/Copy this toolchain to your $THEOS/toolchain path. There will be a ‘‘linux‘‘ folder here by default (should be, atleast...)
- Move/Copy this sdk folder after un-compressing it to $THEOS/sdks
- Now open any theos project you have. By default there is a Makefile.
- you will set the following variables:
TARGET := iphone:clang:13.7 # depends on which old sdk you used
ARCHS = arm64 # only system level apps/binaries use arm64e. but linux doesn't support it so we will set it explicitly to arm64
BASE_HIKARI_PATH = $THEOS/toolchain/<name-of-toolchain-folder>/bin
TARGET_CC = $(BASE_HIKARI_PATH)/clang
TARGET_CXX = $(BASE_HIKARI_PATH)/clang++
TARGET_LD = $(BASE_HIKARI_PATH)/ld64.lld # this can be 'ld', instead of ld.lld or ld64.lld. check the linker name. after 18.2+ builds, it's ld.lld, not ld. the linker is usually ld64.lld from llvm for Mach Os.
SYSROOT = $THEOS/sdks/<iphonesdkfolder>.sdk
- Now, do a quick compile test and see if all goes well. you may get errors regarding a 'module map' deprecation, so just listen to the error and rename that file from .map to .modulemap.
- Now compile again and this time it should suceed.
- Now, you can add flags for Obfuscation.
OBFUSCATED_Flags = -mllvm -enable-cffobf -mllvm -enable-strcry -mllvm -enable-subobf -mllvm -enable-fco -mllvm -ah_objcruntime -mllvm -enable-antihook -mllvm -ah_inline -mllvm -enable-indibran -mllvm -indibran-enc-jump-target -mllvm -ah_antirebind -enable-constenc -mllvm -constenc_times=1 -mllvm -constenc_togv=1 -mllvm -constenc_togv_prob=50 -mllvm -constenc_subxor=1 -mllvm -constenc_subxor_prob=40
IMPORTANT: ->
For llvm 19+ builds, add -mllvm -hikari in Obfuscate_FLAGS.
- BE CAREFUL THIS CAN STRAIN AND CRASH EVEN FUCKING NASA COMPUTERS!
- experiment around with the flags, find the setup that is just right.
- Pro tip: constenc ususally hogs resources and is the main crash causing culprit.
- You can add these flags in ‘‘CFFlags‘‘ and ‘‘CCFlags‘‘ and compile.
-> LLVM19x seems buggy, but below and above it compile just fine on linux. Here's an example:
//main.cpp
#include <iostream>
int main() { std::cout << "Hello, World!"; return 0; }
-> This main.cpp will be our test file to compile.
-> Now, we give the following command:
~/theos/toolchain/my-toolchain5/bin/clang++ -std=c++17 -mllvm -hikari -mllvm --enable-strcry -mllvm --enable-constenc -mllvm --constenc_togv=1 -mllvm -strcry_prob=99 -mllvm --constenc_togv_prob=99 -fuse-ld=$(which ld) main.cpp -o main
-> Change my-toolchain5 to installed toolchain folder name.
-> You can add whatever passes you want, like I did here.
-> Set linker to $(which ld), with command line argument: -fuse-ld, as shown above.
-> Output (My test with LLVM 20.1.5:)
std::mt19937_64 seeded with current timestamp: 1747726121944
Initializing Hikari Core with Revision ID:dfb9a48616df758fae88acf7fc426b9b208ba30d
Running Hikari On main.cpp
Running StringEncryption On main
Post-cleaning work: 0x59b41889f580
Running ConstantEncryption On main
Doing Post-Run Cleanup
Hikari Out
Spend Time: 0.0003421s
-> Check if it worked?
[rage@rage ~]$ strings main | grep "Hello"
[rage@rage ~]$
-> Yes, it worked! You can add more flags as shown above in the steps.
-> If you want ALL flags and want to learn how to use them, do clang++ -v on the toolchain clang, and see usages.
-> Proudly compiled on manjaro linux (i use arch, btw)
-> llvm18+ used to compile these
-> compiled with system llvm, do not use gcc or g++ on linux to compile this. Usually causes errors.
-> Disclaimer: This will have to do with runtime issues, not llvm or clang bugs. you report that to @llvm in llvm-project, not here
none really. just don't do stupid stuff i guess. im not responsible blah blah blah blah i went fucking insane it took me 9 hours for one build and 2 extra hours for after build bug bullshit and don't want someone else to go through it.