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

Custom ransomware file extension #1242

Closed
mssalvatore opened this issue Jun 16, 2021 · 1 comment
Closed

Custom ransomware file extension #1242

mssalvatore opened this issue Jun 16, 2021 · 1 comment
Labels
Complexity: Low Feature Issue that describes a new feature to be implemented. Impact: Medium Ransomware sp/3

Comments

@mssalvatore
Copy link
Collaborator

mssalvatore commented Jun 16, 2021

Description

As a red team member, I want to be able to configure the file extension that the ransomware simulation uses to rename encrypted files, so that I can more accurately mimic specific ransomware threats.

Acceptance Criteria

  • Encrypted files are renamed with a user-provided extension. (Default: ".m0nk3y")
    • Example: my_picture.jpg -> my_picture.jpg.m0nk3y
  • None/empty is a valid extension. The ransomware payload will not rename files if no extension is provided.
  • Any files that already have the user-provided extension are skipped.
  • Ransomware configuration screen includes a field that allows the user to specify a file extension.
  • Unit tests are written and provide comprehensive coverage.
  • Documentation is written that describes how the file extensions are used.
@mssalvatore
Copy link
Collaborator Author

Resolved by #2206

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: Medium Ransomware sp/3
Projects
None yet
Development

No branches or pull requests

1 participant