backdoor-apk is a shell script that simplifies the process of adding a backdoor to any Android APK file. Users of this shell script should have working knowledge of Linux, Bash, Metasploit, Apktool, the Android SDK, smali, etc. This shell script is provided as-is without warranty of any kind and is intended for educational purposes only.
android android-sdk apk android-development smali apktool metasploitA black-box obfuscation tool for Android apps. Obfuscapk is a modular Python tool for obfuscating Android apps without needing their source code, since apktool is used to decompile the original apk file and to build a new application, after applying some obfuscation techniques on the decompiled smali code, resources and manifest. The obfuscated app retains the same functionality as the original one, but the differences under the hood sometimes make the new application very different from the original (e.g., to signature-based antivirus software).
android black-box application app obfuscation apk smali apktool obfuscapkQuickly analyze and reverse engineer Android applications. This software is free to distribute, modify and use with the condition that credit is provided to the creator (1N3@CrowdShield) and is not for commercial use.
android apk reverse-engineering hacking mobile decompile analyze pentest pentesting smali通过精简Smali语法细节来增强反编译代码阅读性,自定义了一种简单语法
smali android dex decompilerCommand line program for modifying apk files
apk jar apktool apk-decompiler apk-editor apksigner-jarsigner command-line smali dexsmali文件,jar包字符串混淆,支持gradle插件
smali jar obfuscate-strings gradle-plugin androidIf you ever have looked at Android applications you know to appreciate the ability of analyzing your target at the most advanced level. Dynamic program analysis will give you a pretty good overview of your applications activities and general behaviour. However sometimes you'll want to just analyze your application without running it. You'll want to have a look at its components, analyze how they interact and how data is tainted from one point to another. This is was the major factor driving the development of smalisca. There are indeed some good reasons for a static code analysis before the dynamic one. Before interacting with the application I like to know how the application has been build, if there is any API and generate all sort of call flow graphs. In fact graphs have been very important to me since they visualize things. Instead of jumping from file to file, from class to class, I just look at the graphs.
android smali reverse-engineering🦅 cli syntax highlighting: any function - any object - 176 languages
syntax highlight cli color console terminal language highlight.js chalk object string function line-numbers 1c abnf accesslog ada apache arduino armasm asciidoc aspectj autohotkey avrasm axapta bash bnf brainfuck cal capnproto ceylon clean clojure-repl cmake coffeescript coq cos cpp crmsh crystal cs csp css dart delphi diff django dns dockerfile dos dsconfig dts dust ebnf elixir elm erb erlang-repl excel fix flix fsharp gams gauss gcode gherkin glsl golo gradle haml handlebars haskell hsp htmlbars http hy inform7 ini irpf90 jboss-cli json julia-repl julia kotlin lasso ldif leaf less lisp livecodeserver livescript llvm lsl makefile markdown mathematica matlab maxima mel mercury mipsasm mizar mojolicious monkey moonscript n1ql nginx nimrod nix nsis objectivec ocaml openscad oxygene parser3 pf pony powershell processing profile prolog protobuf puppet purebasic q qml r rib roboconf routeros rsl ruleslanguage scilab scss shell smali smalltalk sml sqf sql stan stata step21 stylus subunit taggerscript tap tex thrift tp twig typescript vala vbnet vbscript-html verilog vhdl vim x86asm xl xml xquery yaml zephir
We have large collection of open source products. Follow the tags from
Tag Cloud >>
Open source products are scattered around the web. Please provide information
about the open source projects you own / you use.
Add Projects.