Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-r1-0528· DeepSeekHugging Face LMArena Human Preference 140K

draft a recomm

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Mistralmistral-medium-2505’s answer.
  1. User

    draft a recomm

  2. DeepSeek Assistant

    Based on the attack described, here are key security recommendations:

    For Organizations & Security Teams:

    1. Disable Legacy App Passwords (Where Possible): If using modern authentication (e.g., OAuth 2.0), disable the generation of legacy app-specific passwords entirely via Google Workspace Admin console (Security > Authentication > App passwords) to eliminate this attack vector.
    2. Enforce Phishing-Resistant MFA: Mandate hardware security keys (FIDO2/WebAuthn) or certificate-based authentication, which are immune to app password and phishing-based MFA bypasses.
    3. Implement Advanced Anti-Phishing Controls: Deploy email security solutions with strong link scanning, attachment sandboxing, and sender authentication (SPF, DKIM, DMARC) enforcement.
    4. Conduct Targeted Security Awareness: Train users specifically on:
      • Recognizing fake Google security alerts (verify sender address, avoid embedded links).
      • Never generating or entering app-specific passwords in response to an email.
      • Reporting suspicious emails immediately.
    5. Monitor for App Password Usage: Use security monitoring tools to detect unusual app password creation or logins, triggering alerts for investigation.

    For Individual Gmail Users:

    1. Never Create App Passwords Via Email Links: Google will never ask you to generate an app password via an email link. Only create them directly within your Google Account Security settings (myaccount.google.com > Security > App passwords) if absolutely necessary for a legacy device/app.
    2. Use Stronger MFA: Replace SMS/authenticator app codes with a hardware security key (like a YubiKey) for phishing-resistant protection.
    3. Verify Sender & Links: Scrutinize sender email addresses carefully. Never click links or buttons in unexpected security alerts; go directly to myaccount.google.com.
    4. Review Connected Apps: Regularly check (Security > Your connections to third-party apps & services) and remove unused or suspicious app access.
    5. Consider Disabling App Passwords: If you don't use any older apps/devices requiring them, disable app password creation in your Google Account Security settings.

    Rationale: These actions directly address the core vulnerability exploited (phishing for app passwords) by removing the attack vector, implementing stronger authentication, improving user resilience, and enhancing detection.

  3. User

    draft a recommendation to general user to prevent this attack, in 1-2 sentences

  4. DeepSeek Assistant

    Here's a concise recommendation for general users:

    Option 1 (Direct):

    Never generate or enter an app-specific password via an email link. If you need one, go directly to your Google Account Security settings (myaccount.google.com).

    Option 2 (Slightly More Detail):

    Always go directly to your Google Account (myaccount.google.com) for security actions. Google will never ask you to create an app password through an email link or message.

    Why this works: It directly addresses the core phishing tactic (fraudulent emails requesting app passwords) and provides the simple, safe action (go to the official site yourself).

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.