p17860254
/
monkey
forked from p15670423/monkey
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,442 Commits 31 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 04b2ac6bd9 Don't normalize line endings in ransomware_targets test data 
On Windows, git will normalize the line endings of .txt (and other)
files to crlf instead of lf. This is useful for many files, but the
ransomware_target files need unmodified when they are checked out.

By adding an exception in .gitattributes, the files in
monkey/tests/data_for_tests/ransomware_targets are not modified on
windows.
 		2021-06-28 20:52:42 -04:00
.github Add changelog checklist item to pull request template 2021-03-29 12:20:33 -04:00
.swm Swimm: update exercise Add a new System Info Collector (id: OwcKMnALpn7tuBaJY1US). 2021-06-21 22:40:37 +05:30
appimage appimage: Remove `run_appimage.sh` as it is no longer needed 2021-06-03 10:57:23 -04:00
deployment_scripts Removed quotes in deployment_scripts README for first argument of deploy_linux.sh. Related #1108. 2021-06-14 12:54:25 -04:00
docs docs: Reword paragaraph about why ransomware simulation is sufficient 2021-06-25 19:07:32 +05:30
envs Improve exception message, thrown when trying to establish connection to island in BB tests 2021-05-21 08:41:28 +03:00
monkey Merge branch 'ransomware_readme_config_option' into develop 2021-06-28 14:57:18 -04:00
.flake8 Rename vulture_whitelist.py -> vultue_allowlist.py 2021-06-02 13:08:37 +05:30
.gitattributes Don't normalize line endings in ransomware_targets test data 2021-06-28 20:52:42 -04:00
.gitignore Fixed gitignores to exclude some irrelevant files 2021-04-09 14:54:02 +03:00
.gitmodules Refactored ScoutSuite into a separate package rather than submodule 2021-03-17 11:49:33 -04:00
.pre-commit-config.yaml Add vulture pre-commit hook 2021-05-05 19:09:07 +05:30
.travis.yml island: Remove server_config.json.develop 2021-06-03 20:38:13 -04:00
CHANGELOG.md Update encryption/decryption PR numbers in changelog 2021-06-09 10:02:44 -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 Remove training whitespace from README.md 2021-06-20 09:15:57 -04:00
codecov.yml Disable codecov annotations in pull requests 2021-06-22 10:00:23 -04:00
pyproject.toml Only search tests/unit_tests for monkey unit tests 2021-06-03 16:09:57 -04:00
vulture_allowlist.py Remove RansomwareTelem from vulture_allowlist 2021-06-24 15:55:17 -04: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).