From 6d246da91735955489405353caf316a62c43dff7 Mon Sep 17 00:00:00 2001
From: Atharva Mashalkar <atharvam212@gmail.com>
Date: Tue, 20 Oct 2026 16:33:45 +0530
Subject: [PATCH] fix(proxy): avoid the public master-key prefix in the email
 test

The code-quality scan rejects sk-1234. The markup key used that prefix,
so the HTML-escaping test now uses a different key.
---
 tests/unit/proxy/hooks/test_send_invite_email.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/unit/proxy/hooks/test_send_invite_email.py b/tests/unit/proxy/hooks/test_send_invite_email.py
index fec7c63352d..ea4eaf2dbe5 100644
--- a/tests/unit/proxy/hooks/test_send_invite_email.py
+++ b/tests/unit/proxy/hooks/test_send_invite_email.py
@@ -19,7 +19,7 @@ from litellm.proxy.hooks.user_management_event_hooks import UserManagementEventH
 
 _PLAINTEXT_KEY = "sk-plaintext-key-39315"
 _TOKEN_ID = "a1b2c3d4e5f6789012345678abcdef01"
-_MARKUP_KEY = 'sk-1234567890123456</pre><a href="https://attacker.example/login">Activate key</a><pre>'
+_MARKUP_KEY = 'sk-9876543210987654</pre><a href="https://attacker.example/login">Activate key</a><pre>'
 
 
 def _key_created_email_response(key: str = _PLAINTEXT_KEY) -> GenerateKeyResponse: