Description

As a red team member, I want a ransomware simulation that leaves a README.txt in the target directory, as this mimics a common behavior of many ransomware.

Acceptance Criteria

• A README.txt file is left in each directory where files were encrypted.
• The README.txt file includes:
  • An description of Infection Monkey
  • An obvious message or title instructing the user not to panic, as this is only a ransomware simulation.
• The ransomware simulation can be configured so that the README.txt feature is disabled.
• Ransomware configuration screen includes a checkbox that allows the user to enable/disable leaving a readme file.
• Unit tests are written and provide comprehensive coverage.
• Documentation is written that describes how the readme functionality behaves.

• Add a readme enable/disable option to the configuration (0d) - @VakarisZ
• Modify the ransomware payload to leave a README file if feature is enabled (0.25d) - @mssalvatore
• Define contents of README.txt file (0d) - @mssalvatore
• Modify documentation to include details about the README (0d) - @shreyamalviya