Skip to main content

Android Hooking: Writing Xposed Modules

1. Declare the module in AndroidManifest.xml

<manifest xmlns:android=""
    android:versionName="1.0" >

        android:targetSdkVersion="15" />

        android:theme="@style/AppTheme" >
            android:value="true" />
            android:value="List APP Modules and hook Some funtions" />
            android:value="30" />


2. Create a text file called xposed_init (without .txt) in your assets folder with your main class as the content.

& also create a directory named "lib" inside your project and  add XPosedBridgeAPI.jar in it.

Xposed Module Writing

3. Inject package loading process using handleLoadPackage() method

public void handleLoadPackage(final LoadPackageParam lpparam) throws Throwable {
    if (!lpparam.packageName.equals(""))
    XposedBridge.log("we are in SystemUI!");

4. Hook and replace your methods of choice. Don't forget to static import this method:

import static;

Run your code before/after a method. You can determine the returned result of the method using theMethodHookParam.

findAndHookMethod(" ", lpparam.classLoader, "isThisTheMethodToBeHooked", new XC_MethodHook() {
    protected void beforeHookedMethod(MethodHookParam param) throws Throwable {
        // this will be called before the original method is executed
        if (somethingHappens) {
            // modify the result of the original method

    protected void afterHookedMethod(MethodHookParam param) throws Throwable {
        // this will be called after
You can also replace the method completely. If the function has some params, make sure you include them in the findAndHookMethod function call.

findAndHookMethod("com.example.SomeClass", loadPackageParam.classLoader, "getAudioEnabled", Context.class, String.class, new XC_MethodReplacement() {
    protected Object replaceHookedMethod(MethodHookParam param) throws Throwable {
        return true;



Popular posts from this blog

Hacking Windows 10 UWP App: DLL Injection & common Vulnerabilities

I recently started working on  widows 10 Apps( Apps not Applications) security. Before diving deep in hacking terms lets try to understand what's new in Windows 10 UWP( Universal Platform) as compared to old Apps. Lets begin with how apps actually work on windows 10(desktop/tablet). Now windows 10 comes with a container only for running apps inside the isolated environment. By default, /APPCONTAINER(Linker Flag) is off. This option modifies an executable to indicate whether the app must be run in the appcontainer process-isolation environment. Specify /APPCONTAINER for an app that must run in the appcontainer environment—for example, a Windows Store app. (The option is set automatically in Visual Studio when you create a Windows Store app from a template.) For a desktop app, specify /APPCONTAINER:NO or just omit the option. The /APPCONTAINER option was introduced in Windows 8. Now there is no registry entry concept for these app in the System HIVE rather they install they own hiv

Installing vmware-11.0 on Ubuntu 15.04 Using kernel Patch

curl -o /tmp/vmnet-3.19.patch cd /usr/lib/vmware/modules/source tar -xf vmnet.tar patch -p0 -i /tmp/vmnet-3.19.patch tar -cf vmnet.tar vmnet-only rm -r *-only vmware-modconfig --console --install-all References:

SSI Injection Attack

SSIs are directives present on Web applications used to feed an HTML page with dynamic contents. They are similar to CGIs, except that SSIs are used to execute some actions before the current page is loaded or while the page is being visualized. In order to do so, the web server analyzes SSI before supplying the page to the user. The Server-Side Includes attack allows the exploitation of a web application by injecting scripts in HTML pages or executing arbitrary codes remotely. It can be exploited through manipulation of SSI in use in the application or force its use through user input fields. It is possible to check if the application is properly validating input fields data by inserting characters that are used in SSI directives, like:  Code: < ! # = / . " - > and [a-zA-Z0-9] Another way to discover if the application is vulnerable is to verify the presence of pages with extension .stm, .shtm and .shtml. However, the lack of these type of pages does not mean that th