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
Docker-Escape-Miner — Code sample for using exploit CVE-2019-5736 to mine bitcoin with no association to original container or user. | Kitploit
Tools/GitHubGitHub/epsteina16/docker-escape-miner
Privilege EscalationVulnerability AnalysisExploitationRed TeamingPayload DevelopmentContainer Escape
GitHubepsteina16/docker-escape-miner

Docker-Escape-Miner

Code sample for using exploit CVE-2019-5736 to mine bitcoin with no association to original container or user.

View Repository
3356 years agoNot yet reviewed
Share

Using a published Docker exploit to gain root access and run a bitcoin mining script

This uses two open source libraries:

  • nightminer by @ricmoo for python bitcoin mining
  • RunC-CVE-2019-5736 by @twistlock for the docker escape

System Requirements

This was tested on Kali Linux, with Docker version 18.03.0 and RunC version 1.0.0-rc5.

How to Run

  1. Clone the repository, and cd into it.
  2. Run ./setup.
  3. Change settings in config.txt to be your username, password and address for mining server.
  4. Build the docker container using: docker build -t hack .
  5. Run the malicious docker container using: docker run --rm hack
  6. Check to see that the daemon is running with ps -aef | grep python.

What is the result

The docker container escape starts multiple mining daemons which belong to process #1 (the kernel). This means the computers resources are used for mining without the script/compute resources being associated with your container.

How this works

This takes advantage of CVE-2019-5736. When the container is run, docker uses docker-runc to run it, and we access the pid of runc which is running our container. We then pass the execution to another program (overwrite_runc) with the symlink to the runc binary. This symlink points us directly to the file descriptor of the runc binary. This allows us to open the runc file descriptor for writing and overwrite it. By overwriting it with a malicious script, when the container shuts down, it executes the script with root priveleges, allowing us to start a cryptominer.

Warning

This overwrites the runc binary on the testbed, so copying the real one is smart before running this.

Don't use this on real, vulnerable systems.

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.

    795
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    520
  • 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.

    439
  • 4

    redforge

    cybersecurity91/redforge

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

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    267
  • 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.

    264

Explore all tools

Browse our collection of tools

View all tools →