# Guidance Needed on Flow.com Vulnerability Report Submission

**URL:** <https://forum.flow.com/t/guidance-needed-on-flow-com-vulnerability-report-submission/7895>\
**Category:** 🛠 Developer Tools\
**Created:** [June 2, 2025, 4:57pm UTC](https://forum.flow.com/t/guidance-needed-on-flow-com-vulnerability-report-submission/7895 "2025-06-02T16:57:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ridoyp99](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/ridoyp99/32/1831_2.png) [@Ridoyp99](https://forum.flow.com/u/Ridoyp99)\
**Post date:** [June 2, 2025, 4:57pm UTC](https://forum.flow.com/t/guidance-needed-on-flow-com-vulnerability-report-submission/7895/1 "2025-06-02T16:57:06Z")

</div>

Dear Flow Team,

I have discovered a potential vulnerability on flow.com. As per your bug bounty guidelines, I initially submitted the report to **[security@onflow.org](mailto:security@onflow.org)**.

Shortly after, I received an automated response instructing me to submit the report via **HackenProof**. However, upon checking HackenProof, I noticed that the Flow bug bounty program is scheduled to start in **212 days**. There is another program currently open, but it appears to be focused specifically on **smart contracts** , which does not relate to my finding.

Could you please advise me on the correct procedure for submitting this report? I want to ensure the responsible disclosure of this issue through the appropriate channel.

Looking forward to your guidance.