Skip to content

A Frida module to dump, trace or hijack any Il2Cpp application at runtime, without needing the global-metadata.dat file.

License

Notifications You must be signed in to change notification settings

vfsfitvnm/frida-il2cpp-bridge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

frida-il2cpp-bridge

Frida NPM

A Frida module to dump, trace or hijack any Il2Cpp application at runtime, without needing the global-metadata.dat file.

code

Features

  • Dump classes, methods, fields and so on
  • Trace, intercept and replace method calls
  • Mess around with the C# runtime
  • Il2Cpp structs and global metadata (almost) free

Compatibility

Unity version

It should work for any Unity version in the range 5.3.0 - 2022.1.x.

Platforms

Android, Linux, Windows, iOS, macOS are supported. However, only Android and Linux are "tested": expect breakage if you are using another platform.

Testing

Over the time, it was realized that some testing was necessary, as supporting many Unity version makes introducing regressions or faulty features easy. Though it's far from being complete and bullet-proof, there's a minimal testing setup contributors can get advantage of to test their changes.
In order to test frida-il2cpp-bridge, a IL2CPP application is needed (of course). Here are some very useful resources:

Commands

Unity editors (so IL2CPP toolchains) will be downloaded and extracted automatically.

Prerequisites

  1. Only Linux is currently supported;
  2. Make sure to have clang and make installed.

Build IL2CPP assemblies

make assemblies

An assembly (GameAssembly.so) will be built for each of tested Unity versions.

Build IL2CPP assembly for a specific Unity version only

make unity/2019.3.0f1/

Run tests

make test

Tests run against only the installed Unity versions.

Acknowledgements

Thanks to meme and knobse for helping and getting me into this, and to djkaty and nneonneo for providing the Il2Cpp API.

Problems?

Discussions and Wiki are both active. Use them!