worawit/blutter: arm64 Android only, and it compiles the Dart runtime when the executable is missing
Flutter Mobile Application Reverse Engineering Tool
At a glance
- What is it?
- B(l)utter recovers Dart object pools and assembly from a Flutter app by linking against a Dart AOT runtime it builds itself. The README states the limits plainly: Android libapp.so, arm64 only, recent Dart versions, and it opens by telling you to extract the lib directory out of the apk by hand.
- Who is it for?
- Use this when you hold an arm64 Android Flutter binary and need the object pool, the assembly with symbols, or a starting point for a Frida script, and read the scope before you plan around it. Three limits decide whether it works at all: the architecture, the platform, and how old the Dart version in the target is, since the project states it only handles recent Dart versions.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 89 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- worawit/blutter2,824 ★ · +106
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| worawit/blutter | 2.7k | 2.8k |
106 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Android libapp.so, arm64 only, recent Dart versions only
The scope is stated in the second and third lines of the README and there is no hedge on either. The application supports only Android libapp.so, and only the arm64 architecture. The second sentence says the application currently works only against recent Dart versions, which matters because the whole design is keyed to the Dart version in the target: the script reads it out of the flutter engine, then looks for a matching prebuilt executable. A 32-bit or x86 build, an iOS binary, or an app built with an old Dart runtime are all outside what this describes. The todo list confirms the edges from the other side, with entries for reading iOS binaries, for obfuscated apps where many functions are still missing, and for taking an apk or ipa as input. There are no GitHub releases attached to the repository, so the source tree is the distribution.
When the matching executable is missing, it checks out Dart and compiles it
The mechanism has two paths and the script picks between them at runtime. Normally blutter.py detects the Dart version from the flutter engine found in the target and calls the executable already sitting in bin for that version. When no executable exists for the required Dart version, the script automatically checks out the Dart source code and compiles it. That second path is not a small step: the directories at the top of the repository explain what it leaves behind, with a dartsdk directory holding the checkout of the Dart Runtime, a packages directory holding the static libraries of that runtime, a blutter directory with source that needs building against the Dart VM library, and a build directory with the generated projects. The README says the last three can be deleted after finishing the build process, which tells you they are build products rather than inputs.
The compiler floor is C++20 with g++ 13 or Clang 16, and the Debian note is emphatic
The project uses a C++20 formatting library, so it needs a compiler that can handle that and a recent enough standard library around it: g++ 13 or newer, or Clang 16 or newer. The Debian instruction is the sharpest line in the README. Use only a Debian or Ubuntu version that provides gcc 13 or newer from its own main repository, and using a ported gcc on an older Debian or Ubuntu version does not work. The dependency list for that path is short and specific:
apt install python3-pyelftools python3-requests git cmake ninja-build \
build-essential pkg-config libicu-dev libcapstone-devTwo of those entries are doing the heavy lifting for the analysis itself: libcapstone-dev is the disassembler, and libicu-dev is the Unicode library the Dart runtime links against. The recommended platform is Linux, described in the same sentence as only tested on Debian sid and trixie, spelled Deiban in that line while the heading above it reads Debian Unstable.
Four platform recipes, and macOS has two of them for two different toolchains
Installation is four separate recipes, and they are not variations of one another. Debian unstable uses apt with gcc 13. Windows wants git, python 3, the latest Visual Studio with the Desktop development with C++ and C++ CMake tools workloads, then one script to set up the rest, then a specific shell:
python scripts\init_env_win.pyThe README also says to start the x64 Native Tools Command Prompt for that path, which means the build is tied to one developer prompt rather than a general one. macOS splits into two: Sequoia installs XCode and relies on the default compiler, while Ventura and Sonoma install llvm@16 explicitly.
brew install llvm@16 cmake ninja pkg-config icu4c capstone
pip3 install pyelftools requestsSo on macOS the compiler you get depends on which macOS you have, and the older pair pins llvm@16 on purpose. The third-party libraries live in an external directory that the README marks as Windows only, which is how the two icu4c arrangements stay separate.
Four output artifacts, and two of them are complete object dumps
One run writes four things. The asm directory holds the libapp assemblies with symbols. blutter_frida.js is described as the Frida script template for the target application. objs.txt is a complete nested dump of Object from the Object Pool, and pp.txt holds all Dart objects in that pool. The distinction between the two text dumps is the interesting part: one is a traversal of a single class expanded through its nesting, the other is the flat inventory of everything in the pool, which is the list you need when you are looking for a specific type or string and do not yet know where it sits. The Frida file is explicitly a template rather than a finished script, and the todo list asks for a better one covering more internal classes and object modification, so treat the generated script as scaffolding.
One executable per Dart version, named with version, OS and architecture
The bin directory holds the prebuilt executables, named in the form blutter_dartvm with the Dart version, then the operating system, then the architecture. That naming is the lookup key for the whole design, since it is how the script decides whether it can run immediately or has to compile. The update path is the other half of it:
python3 blutter.py path/to/app/lib/arm64-v8a out_dir --rebuildThe README says to update with git pull and then run blutter.py with the rebuild option to force a rebuild of the executable, which is the step you need after updating the tool so that an existing binary is not silently reused. The top level of the repository shows three Python entry points by name, blutter.py, dartvm_fetch_build.py and extract_dart_info.py, alongside the blutter source directory and the scripts directory that holds the Python used for getting and building Dart, plus a development flag for generating a Visual Studio solution.
Taking an apk as input is on the todo list, so the lib directory comes out by hand
The usage section opens with an instruction rather than a command: extract the lib directory from the apk file. Only then does the tool run, against the arm64-v8a directory inside it:
python3 blutter.py path/to/app/lib/arm64-v8a out_dirThe todo list closes the loop on this, with entries for input as apk or ipa and for reading iOS binaries, so the manual extraction step is a known gap rather than a stylistic choice. The argument shape is the same for the development path, where the second argument becomes a build directory and an option asks for a Visual Studio solution to be generated. For a project that analyses more than one app, the practical consequence of all this is that every target needs its lib directory prepared by a separate step, and the analysis itself only begins once that is done.
Editorial conclusion
Use this when you hold an arm64 Android Flutter binary and need the object pool, the assembly with symbols, or a starting point for a Frida script, and read the scope before you plan around it. Three limits decide whether it works at all: the architecture, the platform, and how old the Dart version in the target is, since the project states it only handles recent Dart versions. The apk and ipa inputs are on the todo list rather than implemented, so the extraction step is manual. And when the prebuilt executable for your Dart version is missing, the tool compiles the Dart runtime from a source checkout, which is a long first run rather than an installation.
Frequently asked questions
What platforms can worawit/blutter analyze?
Android only, and only the arm64 build of libapp.so. Reading iOS binaries and accepting an apk or ipa directly are both entries on the project's own todo list rather than implemented features, and obfuscated apps are listed as still missing many functions.
How do I run worawit/blutter against a Flutter app?
Extract the lib directory from the apk first, then pass that directory and an output directory to blutter.py. The script detects the Dart version from the flutter engine and calls the blutter executable matching that version to read information out of libapp.so.
What does worawit/blutter need in order to build?
A C++20 formatting library plus g++ 13 or newer, or Clang 16 or newer. The Debian instruction says to use only a Debian or Ubuntu release that provides gcc 13 or newer from its own main repository, and warns that a ported gcc on an older release does not work.
What files does worawit/blutter produce?
Four of them: assemblies with symbols under asm/, blutter_frida.js as a Frida script template for the target, objs.txt as a complete nested dump of Object from the Object Pool, and pp.txt holding all Dart objects in the Object Pool.
Do I have to build worawit/blutter for every Dart version I meet?
Only when the executable is missing. The bin directory holds executables named by Dart version, operating system and architecture, and if the one for the required version does not exist the script checks out the Dart source and compiles it. After updating the tool, the rebuild option forces the executable to be rebuilt.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/worawit-blutter)Star history chart for your README
[](https://hysenlabs.com/projects/worawit-blutter)Was this useful?