[GH-ISSUE #3569] Feature Request: Support for MQL5 (.ex5) bytecode static analysis or provider integration #1322

New issue

Open

opened 2026-10-16 21:04:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:04:15 +00:00

Owner

Originally created by @c2461630 on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3569

Before submitting

I searched the open and closed issues and pull requests for a related proposal.
I understand the contribution scope must be reviewed before integration; open questions are welcome here.
This request does not include credentials, private samples, or sensitive target data.

Area

Other

Current limitation

REA supports various binaries, but MetaTrader 5's MQL5 compiled program (.ex5) format lacks a secure, local, and AI-assisted workflow for analysis due to its proprietary architecture and heavy obfuscation.

Describe the solution you'd like

Requesting support for MQL5 (.ex5) analysis in REA, including static inspection/triage, provider integration, and behavioral tracing workflows.

Describe alternatives you've considered

Current alternatives rely on unsafe online conversion websites/bots prone to malware, with no legitimate local AI-driven tool available.

Additional context

Adding MQL5 support benefits financial software security auditing and makes REA a premier tool for algorithmic trading reverse engineering.

Use cases

No response

Desired outcome and success criteria

For a selected .ex5 file, show an analysis report containing its file structure, verification logic, indicator formula patterns, or pseudocode representation if possible. A useful result would allow the AI agent to understand the underlying trading logic from a high-level behavioral perspective.

Expected interaction with targets

Not sure yet

Target and scope details (optional)

No response

Verification available so far

Idea only; I need help defining checks

Verification details (optional)

No response

Alternatives considered

No response

Possible direction

No response

References

No response

Originally created by @c2461630 on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3569 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This request does not include credentials, private samples, or sensitive target data. ### Area Other ### Current limitation ### Is your feature request related to a problem? Please describe. REA supports various binaries, but MetaTrader 5's **MQL5 compiled program (.ex5)** format lacks a secure, local, and AI-assisted workflow for analysis due to its proprietary architecture and heavy obfuscation. ### Describe the solution you'd like Requesting support for **MQL5 (.ex5) analysis** in REA, including static inspection/triage, provider integration, and behavioral tracing workflows. ### Describe alternatives you've considered Current alternatives rely on unsafe online conversion websites/bots prone to malware, with no legitimate local AI-driven tool available. ### Additional context Adding MQL5 support benefits financial software security auditing and makes REA a premier tool for algorithmic trading reverse engineering. ### Use cases _No response_ ### Desired outcome and success criteria For a selected .ex5 file, show an analysis report containing its file structure, verification logic, indicator formula patterns, or pseudocode representation if possible. A useful result would allow the AI agent to understand the underlying trading logic from a high-level behavioral perspective. ### Expected interaction with targets Not sure yet ### Target and scope details (optional) _No response_ ### Verification available so far Idea only; I need help defining checks ### Verification details (optional) _No response_ ### Alternatives considered _No response_ ### Possible direction _No response_ ### References _No response_

bsakaguchi added the

triage

enhancement

labels

2026-10-16 21:04:15 +00:00

bsakaguchi referenced this issue

2026-10-17 21:10:23 +00:00

[PR #1322] [MERGED] perf(json): encode streamed JSON iteratively #2799

bsakaguchi added

enhancement

and removed

enhancement