Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
VIKIROOT — CVE-2016-5195 (Dirty COW) PoC for Android 6.0.1 Marshmallow | Kitploit
Tools/GitHubGitHub/hyln9/vikiroot
Android SecurityPrivilege EscalationVulnerability AnalysisExploitationMobile SecurityBinary ExploitationArchived
GitHubhyln9/vikiroot

VIKIROOT

CVE-2016-5195 (Dirty COW) PoC for Android 6.0.1 Marshmallow

View Repository
271103499 years agoNot yet reviewed
Share

VIKIROOT

This is a CVE-2016-5195 PoC for 64-bit Android 6.0.1 Marshmallow (perhaps 7.0 ?), as well as an universal & stable temporal root tool. It does not require a SUID executable or any filesystem changes.

Features

  • SELinux bypass (see below for details).
  • Memory-only: does not modify the filesystem or need special executable.
  • Stable: does not affect stability of your device.
  • Scalable: easy to add new kernel and/or new devices.
  • Reversible: the backdoor is cleared automatically after the root shell ends, which means no reboot is required after usage.

Attention

By "SELinux bypass" I mean the payload will run in init domian even if SELinux is in enforcing mode, however, a patch to sepolicy is still needed for making init domain unconfined. Usually this means a modified boot image is required.

Prerequisite

  • I, Robot by Isaac Asimov.
  • "dirtycow-capable" device.
  • patched sepolicy.

Building

Pre-built binaries are available on the release page. Otherwise, just add NDK standalone toolchain into PATH and run make.

Usage

You may run it through an adb shell (place it under /data/local/tmp) and get a root shell either in the built-in terminal or a remote terminal server such as nc. For details, run it without any parameters.

Troubleshooting

  • firstly please read through the "Attention" part above.
  • "insufficient place for payload" or "unknown kernel": a reboot is required.
  • "waiting for reverse connect shell": please wake up your device, open the clock/alarm app or toggle the bluetooth switch in order to trigger the backdoor.
  • still no luck: please run the "dbg" version and send an e-mail to me with the generated files which are just dump of some part of kernel and don't contain any personal information.

Credits

  • scumjr for the vDSO patching method.
  • Tzul for helping me debug the sepolicy problem.
  • RenaKunisaki for making it work with bionic.

TODO

  • Enrich the kernel database for x86 support and so on.
  • Test it on Android 7 Nougat (help wanted!).
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →