search

M4sc3r4n0 / Evil-Droid

955 stars 402 forks source link

Failed to verify signed artifacts #5

Open rehbarali opened 7 years ago

rehbarali commented 7 years ago

It shows failed to verify signed artifacts. even deleted .android/debug.keystore and entered new one`s but still problem remains. Dependencies are found even updated them manually. whether i choose backdoor(new , old) pr av bypasss it shows the error everytime. [ ✔ ] Metasploit-Framework..............[ found ] [ ✔ ] Xterm.............................[ found ] [ ✔ ] Zenity............................[ found ] [ ✔ ] Aapt..............................[ found ] [ ✔ ] Apktool...........................[ found ] [ ✔ ] Zipalign..........................[ found ] [✔] BYPASS AV APK

[ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Generating apk payload [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Decompiling Payload APK... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Scrubbing the payload contents to avoid AV signatures... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Changing name and icon payload... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Rebuilding APK file... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Checking for ~/.android/debug.keystore for signing... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Attempting to sign the package with your android debug key [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Verifying signed artifacts... [ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [!] Failed to verify signed artifacts

MazenElzanaty commented 7 years ago

Same here [ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Attempting to sign the package with your android debug key [ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [] Verifying signed artifacts... [ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [!] Failed to verify signed artifacts

Ghwapik commented 7 years ago

just delete the keystore from your home files ( .android/debug.keystore )

CrazyGeniuss commented 7 years ago

I did what Ghwapik said but, i still get the same mistake. Please help me!
[!] Failed to verify signed artifacts

Ghwapik commented 7 years ago

this mistake with some apk just change it

adilalkp commented 7 years ago

can you suggest any apps easy to embed a payload?

gussj commented 6 years ago

just install sudo apt install openjdk-9-jdk-headless and try again

gussj commented 6 years ago

I updated apktool too from the website to 2.3.0 (just replace the jar file in Tools folder)

zulfi2000blr commented 6 years ago

please give me a link to download apk jar tool 2.3.0

k-venom commented 6 years ago

still it is not working.....

RVatgit commented 6 years ago

not working

mdj6131 commented 6 years ago

Install Open JDK 11

sudo apt-get install openjdk-11-jdk-headless

remove the old Evil-Droid-master folder

sudo rm -r ~PATH/Evil-Droid-master/

download new one

wget https://codeload.github.com/M4sc3r4n0/Evil-Droid/zip/master

decompress the archive

unzip master && cd Evil-Droid-master/

grant execution priv to the executable

sudo chmod +755 evil-droid && ./evil-droid

k-venom commented 6 years ago

Same problem is coming...There is no change..

Sent from my iPhone

On 27-Jun-2018, at 8:42 PM, mdj6131 notifications@github.com wrote:

Install Open JDK 11

sudo apt-get install openjdk-11-jdk-headless

remove the old Evil-Droid-master folder

sudo rm -r ~PATH/Evil-Droid-master/

download new one

wget https://codeload.github.com/M4sc3r4n0/Evil-Droid/zip/master

decompress the archive

unzip master && cd Evil-Droid-master/

grant execution priv to the executable

sudo chmod +755 evil-droid && ./evil-droid

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

orichalcum17 commented 6 years ago

Hi Everybody, I can not proceed, can someone give me a hand? I receive this message: "Failed to verify signed artifacts" and evil-droid don't generate the .apk file :( Thanks.

xm00ds commented 6 years ago

HELP please i try all but I receive this message: "Failed to verify signed artifacts"

xm00ds commented 6 years ago

if I update the zipalign libc ++ error.

yogeshnarayankar1999 commented 5 years ago

any updates? i got same issue

irfnd commented 5 years ago

[!] Failed to verify signed artifacts

Update apktool.jar to latest version, Check this web And replace the apktool.jar in tools folder.

PhantomX15 commented 5 years ago

[!] Failed to verify signed artifacts

Update apktool.jar to latest version, Check this web And replace the apktool.jar in tools folder.

I updated apktool and checked for the version and it still gives the same issue..

root@kali:~# apktool -version 2.4.0

MrMadhesh commented 5 years ago

Verifying signed artifacts... +++++++++++++++++++++++++++++++++ [! ] Failed to verify signed artifacts

How to solve error?

irfankhan090 commented 5 years ago

Same Problem. [ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [!] Failed to verify signed artifacts

Alyoninthecity commented 5 years ago

How to solve?

ridouanz commented 5 years ago

same problem . pleaase help

jeffreydaniel20959 commented 5 years ago

i tried all the methods given above but none of them works and there are also no other youtube videos or website which explains it.It's frustrating will this work or is it some kind of a joke????

jeffreydaniel20959 commented 5 years ago

where can i contact the developers if anyone can complain about this issue to them

Wh1teR4bb1t commented 5 years ago

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid)

By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar.

The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this (https://ibotpeaches.github.io/Apktool).

So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website.

In practice :

I just tested and it works on my side.

McDonaldsTriad commented 5 years ago

I had the same problems like everyone else in this thread, with Evil-Droid failing to succesfully compile the .apk with the injected payload. Untill I tried out the solution that Wh1teR4bb1t mentions, which thankfully fixed the problem. Your help in solving this problem is very much appreciated, Wh1teR4bb1t!

artozari commented 4 years ago

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid)

By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar.

The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this (https://ibotpeaches.github.io/Apktool).

So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website.

In practice :

  • Download the latest apktool.jar from https://bitbucket.org/iBotPeaches/apktool/downloads/
  • Rename apktool_2.X.X.jar to apktool.jar
  • Remove Evil-Droid-master/tools/apktool.jar
  • Move the downloaded apktool.jar to Evil-Droid-master/tools/
  • (Eventually update the version stated by Evil-Droid-master/tools/doc.txt)

I just tested and it works on my side.

Me Funciono, Muchas gracias, THX so much men!!!

marcosvro commented 4 years ago

sudo apt install openjdk-11-jdk-headless

ahmedsherbi commented 4 years ago

you should install openjdk-13

ahmedsherbi commented 4 years ago

sudo apt install openjdk-13-jdk-headless

Ramkumar492 commented 4 years ago

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid)

By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar.

The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this (https://ibotpeaches.github.io/Apktool).

So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website.

In practice :

* Download the latest apktool.jar from https://bitbucket.org/iBotPeaches/apktool/downloads/

* Rename apktool_2.X.X.jar to apktool.jar

* Remove Evil-Droid-master/tools/apktool.jar

* Move the downloaded apktool.jar to Evil-Droid-master/tools/

* (Eventually update the version stated by Evil-Droid-master/tools/doc.txt)

I just tested and it works on my side.

andreicadar commented 4 years ago

Did the same as Ramkumar492 said with apktool 2.4.1 even modified the doc.txt but still same error [*] Verifying signed artifacts... [ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ] [!] Failed to verify signed artifacts tried with 2.4.0 too, same error

dcld5 commented 4 years ago

there's nothing I can do about this.. "Failed to verify signed artifacts" I've done apt-get upgrade, I've updated the apktool... still the same error over and over again. If only there's some alternatives that did the same stuff as the original evil-droid :(

farooqalk commented 4 years ago

This is so frustrating!! Did everything you guys said but it's still not working....

farooqalk commented 4 years ago

Oh finally it somehow worked after I updated my JDK and replace the apktool.jar file and the document that contains the jar version

pretech86 commented 4 years ago

@farooqgv can you write a detailed steps please ?

catekuser commented 4 years ago

Oh finally it somehow worked after I updated my JDK and replace the apktool.jar file and the document that contains the jar version

Can you please explain in detail step by step?

pretech86 commented 4 years ago

It working with me now also .. I install fatrat and phantom evasion tools requirements and use java 8 and it working

catekuser commented 4 years ago

It working with me now also .. I install fatrat and phantom evasion tools requirements and use java 8 and it working

Hi, does it work for all apk? Can you suggest a working apk please.

pretech86 commented 4 years ago

I don’t think so it will work for all apps , i think it work with old apps versions only until v.4 but you can test it

mpandey67 commented 4 years ago

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid) By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar. The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this (https://ibotpeaches.github.io/Apktool). So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website. In practice :

  • Download the latest apktool.jar from https://bitbucket.org/iBotPeaches/apktool/downloads/
  • Rename apktool_2.X.X.jar to apktool.jar
  • Remove Evil-Droid-master/tools/apktool.jar
  • Move the downloaded apktool.jar to Evil-Droid-master/tools/
  • (Eventually update the version stated by Evil-Droid-master/tools/doc.txt)

I just tested and it works on my side.

Me Funciono, Muchas gracias, THX so much men!!!

yes this worked perfectly for me!!!!!

xm00ds commented 4 years ago

What features should the apk have to allow to embed the code that allows remote access?

xm00ds commented 4 years ago

I have done what they say manishkali67 and Wh1teR4bb1t I would like to recommend an apk with which they have tried and review why I think it is a theme of signatures in the apk what does not allow to do the reassembly

xm00ds commented 4 years ago

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid) By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar. The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this (https://ibotpeaches.github.io/Apktool). So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website. In practice :

  • Download the latest apktool.jar from https://bitbucket.org/iBotPeaches/apktool/downloads/
  • Rename apktool_2.X.X.jar to apktool.jar
  • Remove Evil-Droid-master/tools/apktool.jar
  • Move the downloaded apktool.jar to Evil-Droid-master/tools/
  • (Eventually update the version stated by Evil-Droid-master/tools/doc.txt)

I just tested and it works on my side.

Me Funciono, Muchas gracias, THX so much men!!!

yes this worked perfectly for me!!!!!

I download the 2.2.4 but the question is should I install that version or the latest apktool that is the version 29 Nov 2019 - Apktool v2.4.1 Released Details / Download

mpandey67 commented 4 years ago

yes try version 2.4.1

On Thu, Feb 20, 2020 at 4:23 PM xm00ds notifications@github.com wrote:

The problem comes from the use of an outdated apktool.jar by ED (Evil-droid) By looking on the source code and Evil-droid files, we can notice than ED don't use system apktool software, but embed its own one. It is located in Evil-Droid-master/tools/apktool.jar. The version of this specific file is apktool 2.2.4. But according to the main website, the version is 2.4.0 at the time of writing this ( https://ibotpeaches.github.io/Apktool). So you have to replace Evil-Droid-master/tools/apktool.jar by an updated apktool.jar downloaded directly from the main website. In practice :

  • Download the latest apktool.jar from https://bitbucket.org/iBotPeaches/apktool/downloads/
  • Rename apktool_2.X.X.jar to apktool.jar
  • Remove Evil-Droid-master/tools/apktool.jar
  • Move the downloaded apktool.jar to Evil-Droid-master/tools/
  • (Eventually update the version stated by Evil-Droid-master/tools/doc.txt)

I just tested and it works on my side.

Me Funciono, Muchas gracias, THX so much men!!!

yes this worked perfectly for me!!!!!

I download the 2.2.4 but the question is should I install that version or the latest apktool that is the version 29 Nov 2019 - Apktool v2.4.1 Released Details / Download

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/M4sc3r4n0/Evil-Droid/issues/5?email_source=notifications&email_token=AMQV5QB5N2WV32LI3FQ3B3TRD3YFXA5CNFSM4EDT6J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMQGIEA#issuecomment-589325328, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMQV5QBUUFE5BAUWKTQ7V7LRD3YFXANCNFSM4EDT6J5A .

xm00ds commented 4 years ago

[!] Failed to verify signed artifacts

Update apktool.jar to latest version, Check this web And replace the apktool.jar in tools folder.

I just replaced the apktool.jar with the latest version 2.4.1 and nothing follows this problem

xm00ds commented 4 years ago

and use the 2 menu options 2 and 3 Old NEW and the problem persists I don't understand what I should do

mpandey67 commented 4 years ago

The folder in which you stored JDK tool there will be an TXT file just open it and change the version to the current version you download eg 2.4.1 . Save it use the option no. 3 in evil-droid thet is new and one important note here when you will be asked to enter the name of the file to be save don't save name with spaces try only one word. As you asked for which apk it might worked I think almost all I tried it with instagram.

On Fri 21 Feb, 2020, 9:00 AM xm00ds, notifications@github.com wrote:

and use the 2 menu options 2 and 3 Old NEW and the problem persists I don't understand what I should do

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/M4sc3r4n0/Evil-Droid/issues/5?email_source=notifications&email_token=AMQV5QA6WYPHJTWASTM76ULRD5DEDA5CNFSM4EDT6J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMRML5Q#issuecomment-589481462, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMQV5QC4P3O453NJNNMQUBTRD5DEDANCNFSM4EDT6J5A .

Harris333-rgb commented 4 years ago

Le dossier dans lequel vous avez stocké l'outil JDK, il y aura un fichier TXT, ouvrez-le et changez la version à la version actuelle que vous téléchargez, par exemple 2.4.1. Enregistrez-le en utilisant l'option no. 3 dans evil-droid thet est nouveau et une note importante ici quand il vous sera demandé d'entrer le nom du fichier à enregistrer ne pas enregistrer le nom avec des espaces essayez un seul mot. Comme vous avez demandé quel apk cela pourrait fonctionner, je pense que presque tout ce que j'ai essayé avec instagram. … Le ven 21 fév 2020, 09:00 xm00ds, @.***> a écrit: et utilisez les 2 options de menu 2 et 3 Old NEW et le problème persiste Je ne comprends pas ce que je dois faire - Vous recevez ceci parce que vous avez commenté. Répondre à cet e - mail directement, voir sur GitHub < # 5 ? Email_source = notifications & email_token = AMQV5QA6WYPHJTWASTM76ULRD5DEDA5CNFSM4EDT6J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMRML5Q # issuecomment-589481462> ou unsubscribe < https://github.com/notifications/unsubscribe-auth/AMQV5QC4P3O453NJNNMQUBTRD5DEDANCNFSM4EDT6J5A >.

Merci ça marche!

aayushdha commented 4 years ago

Install Open JDK 11

sudo apt-get install openjdk-11-jdk-headless

remove the old Evil-Droid-master folder

sudo rm -r ~PATH/Evil-Droid-master/

download new one

wget https://codeload.github.com/M4sc3r4n0/Evil-Droid/zip/master

decompress the archive

unzip master && cd Evil-Droid-master/

grant execution priv to the executable

sudo chmod +755 evil-droid && ./evil-droid

lund mdrchod bsdke bina lund ke chutiye bhadve