-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jeb2frida Uses Function Alias Instead of Native Function Name #1
Comments
Ah yes, this is a bug indeed. I need to fix it. |
You should be using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I rename a function or class in JEB and use the jeb2frida script to generate a Frida hook, the alias I used when renaming the function/class is included in the jeb2frida output instead of the actual class/function name in the APK. Clearly, the Frida runtime will be unable to hook routines that I've renamed with JEB since the app runtime uses the native names. This also occurs with obfuscated code using unicode function/class names outside of the printable range of characters.
Example, JEB tells me a function is defined as this when I hover my cursor over it
However, JEB auto generated names for this class for me (otherwise the names where
[]
). When I use the jeb2frida script I received this:In this particular case, I think I needed
This is reproducible by simply renaming a function in JEB and using the jeb2frida script on that function. The produced code uses the new function name instead of the natural one (which is required for Frida to successfully hook it).
Can the jeb2frida script be updated to use the native names of functions/classes?
The text was updated successfully, but these errors were encountered: