🛡️ Sentinel: [CRITICAL/HIGH] Fix Hardcoded OTP Authentication Bypass

[dhaatrik]

🎯 What:

Fixed a critical security vulnerability where a hardcoded OTP (1234) allowed bypassing authentication in the Login component.

⚠️ Risk:

Any user could gain unauthorized access to any account by simply entering the hardcoded '1234' OTP, bypassing the intended security verification process. This posed a severe risk of account takeover and data exposure.

🛡️ Solution:

• Removed the hardcoded conditional check for otp === '1234'.
• Implemented a standard fetch call to a simulated backend endpoint (/api/auth/verify-otp) for secure validation.
• Re-enabled the '1234' bypass strictly for local development using import.meta.env.DEV.
• Improved UX by dynamically updating the OTP placeholder based on the environment.
• Added a comprehensive Vitest test suite to ensure the bypass is disabled in production environments.
• Recorded the vulnerability and mitigation in the Sentinel security log.

---

PR created automatically by Jules for task 480955236592831112 started by @DhaatuTheGamer

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.