From f0d4032dfa9b73b0b5b6c0c098a087ca6a0a25fb Mon Sep 17 00:00:00 2001
From: "Leslie H. Cheung" <51898510+lezzokafka@users.noreply.github.com>
Date: Thu, 2 May 2024 12:01:32 +0800
Subject: [PATCH] Update SECURITY.md (#1420)

Signed-off-by: Leslie H. Cheung <51898510+lezzokafka@users.noreply.github.com>
---
 SECURITY.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SECURITY.md b/SECURITY.md
index bd8922f4a7..ac1f3d2b53 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -14,6 +14,6 @@ Once we receive a vulnerability report, Crypto.org will take these steps to addr
 4. Crypto.org will publicly release the security patch for the vulnerability, and acknowledge the security fix in the release notes once the issue has been resolved. Public release notes can reference to the person or people who reported the vulnerability, unless they wish to stay anonymous.
 
 ## Contact Us
-If you find a security issue, you can report it on the [Cronos Immunefi Bug Bounty Program](https://immunefi.com/bounty/cronos/) or you can contact our team directly at [chain-security@crypto.com](mailto:chain-security@crypto.com).
+If you find a security issue, you can report it on the [Hackenproof Bug Bounty Program](https://hackenproof.com/cronos) or you can contact our team directly at [chain-security@crypto.com](mailto:chain-security@crypto.com).
 To communicate sensitive information, you can use the latest key in the 
 [cryptocom's Keybase account](https://keybase.io/cryptocom/pgp_keys.asc) or use its [chat functionality](https://keybase.io/cryptocom/chat).