p34709852
/
monkey
forked from p15670423/monkey
1
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity
4,489 Commits 30 Branches 0 Tags 47 MiB
Python 73.1%
JavaScript 13.8%
CSS 5.7%
TypeScript 2.6%
HCL 1.6%
Other 3.1%
Go to file
Mike Salvatore 2d971d95fc build: select server and logger config at runtime in appimage 2021-03-31 07:37:49 -04:00
.github Add changelog checklist item to pull request template 2021-03-29 12:20:33 -04:00
.swm Swimm: update unit Define what your new PBA does (id: xYkxB76pK0peJj2tSxBJ). 2021-02-18 16:51:52 +02:00
ci_scripts Fixed travis script bug, where flake8 didn't pick up its configuration file 2020-11-06 13:18:03 +02:00
deployment_scripts build: select server and logger config at runtime in appimage 2021-03-31 07:37:49 -04:00
docker bump duckerfile version 2020-04-01 15:33:27 +03:00
docs Merge branch 'release/1.10.0' into develop 2021-03-30 15:59:20 -04:00
envs Fixed tunneling test configuration template 2021-03-19 16:53:31 +02:00
monkey build: select server and logger config at runtime in appimage 2021-03-31 07:37:49 -04:00
.gitignore Created code that generates default server_config.json, so we don't need to track this file on git and remember not to commit credentials. 2020-08-14 15:44:47 +03:00
.gitmodules Refactored ScoutSuite into a separate package rather than submodule 2021-03-17 11:49:33 -04:00
.travis.yml cc: deploy "develop" environment by default 2021-03-31 07:36:07 -04:00
CHANGELOG.md Add empty CHANGELOG.md file 2021-03-29 12:18:47 -04:00
CONTRIBUTING.md Update slack links in documentation 2021-01-25 10:35:39 -05:00
LICENSE Add SecureAuth Corporation acknowledgement to LICENSE.md 2021-02-22 17:44:15 +05:30
README.md job posting 2021-03-29 10:10:22 -04:00
codecov.yml Fix codecov.io integration 2021-01-14 09:24:37 -05:00

README.md

Infection Monkey

GitHub release (latest by date)

Build Status codecov

GitHub stars GitHub commit activity

Data center Security Testing Tool

Welcome to the Infection Monkey!

The Infection Monkey is an open source security tool for testing a data center's resiliency to perimeter breaches and internal server infection. The Monkey uses various methods to self propagate across a data center and reports success to a centralized Monkey Island server.

The Infection Monkey is comprised of two parts:

  • Monkey - A tool which infects other machines and propagates to them.
  • Monkey Island - A dedicated server to control and visualize the Infection Monkey's progress inside the data center.

To read more about the Monkey, visit infectionmonkey.com.

💥 We're Hiring 💥

We are looking for a strong, full-stack developer with a passion for cybersecurity to join the Infection Monkey development team. Infection Monkey is an open-source, automated, breach and attack simulation platform, consisting of a worm-like agent and C&C server. This is a remote position and is open world-wide. If you're excited about Infection Monkey, we want to see your resume. You can learn more about Infection Monkey on our website.

For more information, or to apply, see the official job post here.

Screenshots

Map

Security report

Zero trust report

ATT&CK report

Main Features

The Infection Monkey uses the following techniques and exploits to propagate to other machines.

  • Multiple propagation techniques:
    • Predefined passwords
    • Common logical exploits
    • Password stealing using Mimikatz
  • Multiple exploit methods:
    • SSH
    • SMB
    • WMI
    • Shellshock
    • Conficker
    • SambaCry
    • Elastic Search (CVE-2015-1427)
    • Weblogic server
    • and more, see our Documentation hub for more information about our RCE exploiters.

Setup

Check out the Setup page in the Wiki or a quick getting started guide.

The Infection Monkey supports a variety of platforms, documented in our documentation hub.

Building the Monkey from source

To deploy development version of monkey you should refer to readme in the deployment scripts folder or follow documentation in documentation hub.

Build status

Branch Status
Develop Build Status
Master Build Status

Tests

Unit Tests

In order to run all of the Unit Tests, run the command python -m pytest in the monkey directory.

To get a coverage report, first make sure the coverage package is installed using pip install coverage. Run the command coverage run -m unittest in the monkey directory and then coverage html. The coverage report can be found in htmlcov.index.

Blackbox tests

In order to run the Blackbox tests, refer to envs/monkey_zoo/blackbox/README.md.

License

Copyright (c) Guardicore Ltd

See the LICENSE file for license rights and limitations (GPLv3).