AuraStealer update

[enzok]

Add more data sections that may contain the configuration

[gemini-code-assist]

Summary of Changes

Hello @enzok, 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 enhances the AuraStealer module by expanding its capability to locate and extract configuration data from Portable Executable (PE) files. The primary change involves modifying the section identification logic to search for configuration within both the standard .data section and the "UPX1" section, which is often used by packed executables. This update aims to improve the reliability of configuration extraction, especially for samples that might use different packing or obfuscation techniques.

Highlights

• Enhanced Configuration Extraction: The extract_config function in AuraStealer.py now checks additional PE sections, specifically "UPX1", to locate configuration data, improving its robustness.
• Improved Section Identification: The logic for identifying relevant PE sections has been refactored to iterate through all sections and decode their names, allowing for more flexible matching.

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

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

The pull request updates the extract_config function in AuraStealer.py to improve how data sections are identified within PE files. The changes replace a try-except block with a more explicit loop that iterates through PE sections, decodes their names, and checks for exact matches against UPX1 or .data. This enhances robustness and clarity in locating relevant configuration data sections.

[gemini-code-assist]

The original code used s.Name.find(b".data") != -1 which would match any section name containing .data as a substring. The updated code uses name in ("UPX1", ".data") which requires an exact match for the decoded and null-stripped section name. This is a more precise approach for standard section names and UPX1. Please confirm that the intent is to only match these exact names and not any section containing .data as a substring, as this change in matching logic could alter behavior for non-standard PE files.