Full Report
Posted by Jasika Bawa, Andy Lim, and Xinghui Lu, Google Chrome Security Tech support scams are an increasingly prevalent form of cybercrime, characterized by deceptive tactics aimed at extorting money or gaining unauthorized access to sensitive data. In a tech support scam, the goal of the scammer is to trick you into believing your computer has a serious problem, such as a virus or malware infection, and then convince you to pay for unnecessary services, software, or grant them remote access to your device. Tech support scams on the web often employ alarming pop-up warnings mimicking legitimate security alerts. We've also observed them to use full-screen takeovers and disable keyboard and mouse input to create a sense of crisis. Chrome has always worked with Google Safe Browsing to help keep you safe online. Now, with this week's launch of Chrome 137, Chrome will offer an additional layer of protection using the on-device Gemini Nano large language model (LLM). This new feature will leverage the LLM to generate signals that will be used by Safe Browsing in order to deliver higher confidence verdicts about potentially dangerous sites like tech support scams. Initial research using LLMs has shown that they are relatively effective at understanding and classifying the varied, complex nature of websites. As such, we believe we can leverage LLMs to help detect scams at scale and adapt to new tactics more quickly. But why on-device? Leveraging LLMs on-device allows us to see threats when users see them. We’ve found that the average malicious site exists for less than 10 minutes, so on-device protection allows us to detect and block attacks that haven't been crawled before. The on-device approach also empowers us to see threats the way users see them. Sites can render themselves differently for different users, often for legitimate purposes (e.g. to account for device differences, offer personalization, provide time-sensitive content), but sometimes for illegitimate purposes (e.g. to evade security crawlers) – as such, having visibility into how sites are presenting themselves to real users enhances our ability to assess the web. How it works At a high level, here's how this new layer of protection works. Overview of how on-device LLM assistance in mitigating scams works When a user navigates to a potentially dangerous page, specific triggers that are characteristic of tech support scams (for example, the use of the keyboard lock API) will cause Chrome to evaluate the page using the on-device Gemini Nano LLM. Chrome provides the LLM with the contents of the page that the user is on and queries it to extract security signals, such as the intent of the page. This information is then sent to Safe Browsing for a final verdict. If Safe Browsing determines that the page is likely to be a scam based on the LLM output it receives from the client, in addition to other intelligence and metadata about the site, Chrome will show a warning interstitial. This is all done in a way that preserves performance and privacy. In addition to ensuring that the LLM is only triggered sparingly and run locally on the device, we carefully manage resource consumption by considering the number of tokens used, running the process asynchronously to avoid interrupting browser activity, and implementing throttling and quota enforcement mechanisms to limit GPU usage. LLM-summarized security signals are only sent to Safe Browsing for users who have opted-in to the Enhanced Protection mode of Safe Browsing in Chrome, giving them protection against threats Google may not have seen before. Standard Protection users will also benefit indirectly from this feature as we add newly discovered dangerous sites to blocklists. Future considerations The scam landscape continues to evolve, with bad actors constantly adapting their tactics. Beyond tech support scams, in the future we plan to use the capabilities described in this post to help detect other popular scam types, such as package tracking scams and unpaid toll scams. We also plan to utilize the growing power of Gemini to extract additional signals from website content, which will further enhance our detection capabilities. To protect even more users from scams, we are working on rolling out this feature to Chrome on Android later this year. And finally, we are collaborating with our research counterparts to explore solutions to potential exploits such as prompt injection in content and timing bypass.
Analysis Summary
# Best Practices: Using AI to Stop Tech Support Scams in Chrome
## Overview
These practices focus on leveraging Artificial Intelligence (AI) within the Google Chrome browser to proactively detect and mitigate tech support scams, ensuring users are protected from common social engineering tactics designed to steal data or money.
## Key Recommendations
### Immediate Actions
1. **Ensure Chrome is Updated:** Verify that all user endpoints are running the latest version of Google Chrome to incorporate the most recent AI-powered scam detection models. (Implied: Automatic updates should be enabled).
2. **Enable Real-time Protection:** Confirm that "Safe Browsing" real-time protection features are active for all user profiles browsing the web via Chrome.
### Short-term Improvements (1-3 months)
1. **Monitor Scam Trends:** Establish a process to regularly review reports of new tech support scam vectors (e.g., specific warning messages, deceptive URLs) to inform internal security policies or client-side alerts if using enterprise management tools.
2. **User Education on Deceptive Interference:** Circulate internal advisories or mandatory security snippets educating employees on how tech support scams manifest in browsers (e.g., full-screen warnings, lockups) and the appropriate response (e.g., closing the tab/browser, ignoring prompts).
### Long-term Strategy (3+ months)
1. **Integrate AI Detection Feedback Loop:** Work with IT/security (or rely on built-in Google mechanisms) to ensure that detected and reported scam attempts contribute to improving local/cloud-based AI models, thus enhancing future protection efficacy.
2. **Develop Custom Blocklists (If Applicable):** For managed environments, implement a process to ingest threat intelligence regarding known scam domains or patterns and integrate these into browser security policies to supplement the default AI protection.
## Implementation Guidance
### For Small Organizations
- **Rely on Default Settings:** Ensure all user devices have automatic updates enabled for Chrome. Since the AI feature is baked into the core browser functionality, minimizing configuration deviations maximizes protection.
- **Mandate Safe Browsing:** Use basic endpoint management (if available) or policy enforcement to ensure Safe Browsing is set to the highest protection level.
### For Medium Organizations
- **Enterprise Policy Check:** Review existing Chrome Enterprise policies (via GPO, Intune, etc.) to ensure no policy explicitly degrades or disables Safe Browsing features or necessary telemetry that feeds into security effectiveness.
- **Baseline Reporting:** Track the frequency and type of security warnings generated by Chrome for users to gauge the effectiveness of built-in defenses against local threats.
### For Large Enterprises
- **Audit Third-Party Extensions:** Scan for and remove any browser extensions that manipulate window behavior or dialog boxes, as malicious extensions can mimic or overload legitimate anti-scam features.
- **Enhance Incident Response Playbook:** Update the Incident Response Plan to specifically include steps for handling potential tech support scam compromises (e.g., advising users not to call listed numbers, securing credentials if a fake login page was visited).
## Configuration Examples
*(Note: The provided context describes a Google-developed feature integrated directly into Chrome, meaning specific user-side configuration for the AI itself is generally abstracted away. The recommendations below refer to necessary prerequisites.)*
**Enabling Safe Browsing Protection (Conceptual via Policy Example - Adjust based on actual management tools):**
| Setting/Configuration | Value | Actionable Step |
| :--- | :--- | :--- |
| Safe Browsing Level | Enhanced Protection | Configure policy to enforce 'Enhanced Protection' level for real-time security checks. |
| Auto-Updates | Enabled | Ensure Chrome update mechanism is functional across all endpoints. |
## Compliance Alignment
While the article does not mention specific compliance mandates, protecting users from prevalent online threats aligns with general security principles:
- **NIST Cybersecurity Framework (CSF):** Primarily aligns with **Identify (ID.SC)** and **Protect (PR.PT)** functions regarding continuous monitoring and protective measures for access and use of information systems.
- **ISO/IEC 27001:** Supports **A.12.1.2 (Information Security Function)** and **A.18.1.4 (Compliance with Legal and Contractual Requirements)** by demonstrating due diligence in protecting end-user systems from known social engineering attacks.
- **CIS Critical Security Controls:** Aligns with controls focused on **Secure Configuration of Enterprise Assets and Software** and **Boundary Defense**.
## Common Pitfalls to Avoid
- **Disabling Safe Browsing:** Administrators disabling Safe Browsing or "Enhanced Protection" to "improve performance" or reduce nuisance alerts, thereby removing the AI-based detection layer.
- **Ignoring Browser Updates:** Allowing users to remain on outdated Chrome versions where critical anti-scam model improvements have not yet been deployed.
- **Assuming Native Protection is Enough:** Believing that client-side AI completely eliminates the need for comprehensive user awareness training regarding social engineering techniques.
## Resources
- **Chrome Security Documentation:** Refer to official Google Chrome security documentation for verifying current Safe Browsing configuration states. (Defanged URL: `[Search for 'Chrome Safe Browsing configuration']`)
- **Internal Threat Intelligence Reporting:** Utilize internal incident reporting channels to document successfully blocked scam attempts to aid security posture review.