Go to file
ophirharpazg 5bf6f654e1 deleted unused ports 2020-09-02 12:36:00 +03:00
.github Update PULL_REQUEST_TEMPLATE.md 2020-08-13 20:50:15 +03:00
deployment_scripts Merge pull request #624 from guardicore/623/get-version-from-github-api 2020-07-14 11:16:41 +03:00
docker bump duckerfile version 2020-04-01 15:33:27 +03:00
docs fix Docs page and add to report 2020-09-01 14:16:22 +03:00
envs Fix or noqa some python linter errors 2020-08-31 14:13:56 +03:00
monkey deleted unused ports 2020-09-02 12:36:00 +03: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 Changed submodule URL to new fork 2020-08-25 00:38:52 +03:00
.travis.yml See https://eslint.org/docs/rules/no-prototype-builtins 2020-08-31 17:16:53 +03:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-11-05 13:59:42 +02:00
LICENSE Changed name to fit Github standard 2016-03-01 17:54:01 +02:00
README.md Documentation framework -> hub 2020-08-05 19:12:30 +03: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.

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).