Add evasion_veh.py for VEH detection

[kevross33]

Kazuar APT 8490daab736aa638b500b27c962a8250bbb8615ae1c68ef77494875ac9d2ada2.

this appears to be part of an injection process actually as shown below. I am still working on these detections for inter-process communication (as I was using Kazuar as it uses multiple backdoor components that communicate through inter-process communication methods but it appears I caught here the injection from the main process into explorer in a stealthy way.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 Cuckoo Sandbox signature designed to identify the use of Vectored Exception Handlers (VEH) by suspicious processes. This detection capability is crucial for uncovering advanced evasion and injection techniques, as demonstrated by the Kazuar APT, which leverages VEH to stealthily inject code and hijack execution flow.

Highlights

• New Signature for Vectored Exception Handling (VEH): A new Cuckoo signature, evasion_veh.py, has been added to detect the registration of Vectored Exception Handlers (VEH), a technique often employed by malware for execution flow hijacking and evasion.

🧠 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/evasion_veh.py
  • Added a new signature to detect the registration of Vectored Exception Handlers (VEH).
  • Implemented logic to check for calls to RtlAddVectoredExceptionHandler or AddVectoredExceptionHandler.
  • Assigned relevant categories (evasion, execution, injection) and MITRE ATT&CK TTPs (T1055, T1574).

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new Cuckoo signature, evasion_veh.py, to detect the registration of Vectored Exception Handlers (VEH), a technique associated with malware evasion and process injection. The implementation is sound, but I have provided feedback to simplify the signature's logic by leveraging the base class's features more effectively. This change also corrects a typo in an API argument name, which is crucial for the signature's functionality.