We take security vulnerabilities seriously. If you believe you have found a security issue related to this project (e.g., decompiler evasion, return address manipulation, abnormal control flow transfer, or any other technique discussed in our research), please follow the reporting process below.

Preferred Method: Send an email to therustymate@gmail.com
Alternative Method: Open a private security advisory on our GitHub repository.

Please include the following information in your report:

• Description of the vulnerability or unexpected behavior
• Steps to reproduce (including binary samples, input data, or environment details if possible)
• Potential impact (e.g., control flow integrity bypass, decompiler misanalysis, etc.)
• Suggested mitigation or fix (if any)

We kindly ask that you:

• Do not publicly disclose the vulnerability without giving us reasonable time to address it.
• Do not use the vulnerability to harm users, systems, or data.
• Do not exploit the vulnerability beyond what is necessary to demonstrate the issue.

We will acknowledge your report within 3 business days and work with you to understand, verify, and resolve the issue.

This security reporting policy applies to:

• The core library / binary analysis components
• Any documented techniques (e.g., return address manipulation)

• We will not take legal action against good-faith reporters who follow responsible disclosure.
• We will give credit (if desired) in any public disclosure or changelog.
• We will keep you updated on the status of your report.