Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ransomware README.txt #1244

Closed
4 tasks done
mssalvatore opened this issue Jun 16, 2021 · 0 comments
Closed
4 tasks done

Ransomware README.txt #1244

mssalvatore opened this issue Jun 16, 2021 · 0 comments
Labels
Complexity: Low Feature Issue that describes a new feature to be implemented. Impact: Low sp/2

Comments

@mssalvatore
Copy link
Collaborator

mssalvatore commented Jun 16, 2021

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Low Feature Issue that describes a new feature to be implemented. Impact: Low sp/2
Projects
None yet
Development

No branches or pull requests

1 participant