Skip to content

Create sig for likely ransomware asynchronous encryption#535

Open
kevross33 wants to merge 1 commit intoCAPESandbox:masterfrom
kevross33:patch-99
Open

Create sig for likely ransomware asynchronous encryption#535
kevross33 wants to merge 1 commit intoCAPESandbox:masterfrom
kevross33:patch-99

Conversation

@kevross33
Copy link
Contributor

Lockbit
image

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new detection mechanism aimed at identifying ransomware that utilizes asynchronous encryption techniques. By observing the binding of numerous files to I/O Completion Ports, the new signature helps to flag suspicious processes that might be encrypting user data, thereby enhancing the system's ability to detect and respond to ransomware threats.

Highlights

  • New Ransomware Signature: A new signature, RansomwareIOCPAsynchronousEncryption, has been added to detect potential ransomware activity. This signature focuses on the binding of a large number of files to I/O Completion Ports (IOCP), which is indicative of asynchronous encryption often used by ransomware.
  • IOCP File Monitoring: The signature monitors NtSetInformationFile calls to identify when files are associated with IOCP. It tracks unique file paths and triggers if more than 50 distinct files are bound to IOCP, indicating suspicious behavior.
  • Ransomware TTP Mapping: The signature is mapped to MITRE ATT&CK technique T1486 (Data Encrypted for Impact), categorizing it under 'ransomware' with a severity of 4 and confidence of 80.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • modules/signatures/windows/ransomware_asynchronous_encryption.py
    • Added new signature file for ransomware detection.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new Cuckoo signature for detecting potential ransomware activity that uses asynchronous encryption with I/O Completion Ports. The overall logic is good. I've provided a few suggestions to improve the code's readability and maintainability by removing an unused variable, simplifying a conditional statement, and refactoring a method to be more concise.

def __init__(self, *args, **kwargs):
Signature.__init__(self, *args, **kwargs)
self.iocp_files = set()
self.example_file = None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The instance variable self.example_file is initialized but never used within the class. It should be removed to improve code clarity and eliminate dead code.

def on_call(self, call, process):
info_class = self.get_argument(call, "FileInformationClass")

if info_class == 30 or str(info_class) == "30" or str(info_class).upper() == "FILECOMPLETIONINFORMATION":
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The condition to check info_class is a bit verbose and can be simplified. You can make it more readable and robust by converting info_class to an uppercase string and checking if it's one of the expected values.

Suggested change
if info_class == 30 or str(info_class) == "30" or str(info_class).upper() == "FILECOMPLETIONINFORMATION":
if str(info_class).upper() in ("30", "FILECOMPLETIONINFORMATION"):

Comment on lines +55 to +62
ret = False
if len(self.iocp_files) > 50:
self.data.append({
"total_files_bound_to_iocp": len(self.iocp_files),
})
ret = True

return ret
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The on_complete method can be made more concise by removing the ret flag variable and returning directly. This is a more common and idiomatic pattern in Python.

Suggested change
ret = False
if len(self.iocp_files) > 50:
self.data.append({
"total_files_bound_to_iocp": len(self.iocp_files),
})
ret = True
return ret
if len(self.iocp_files) > 50:
self.data.append({
"total_files_bound_to_iocp": len(self.iocp_files),
})
return True
return False

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant