Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Google Research

Google Research Vendor Cyber Rating & Cyber Score

research.google

From conducting fundamental research to influencing product development, our research teams have the opportunity to impact technology used by billions of people every day. We aspire to make discoveries that impact everyone, and sharing our research and tools to fuel progress in the field is fundamental to our approach.


Google Research A.I CyberSecurity Scoring

Google Research
Company Information
Website:https://research.google/
Employees number:None
Number of followers:362,436
NAICS:513
Industry Type:Technology, Information and Internet
Homepage:research.google
Google Research Risk Score (AI oriented)
Between 700 and 749
logo
Google ResearchTechnology, Information and Internet
Updated:
11/05/2026
712/1000
Moderate
Ba
AaaAaABaaBaBCaaCaC
Powered by our proprietary A.I cyber incident model
Insurance prefers TPRM score to calculate premium
Google Research Global Score (TPRM)
xxxx
logo
Google ResearchTechnology, Information and Internet
•••
Score locked
Instant access to detailed risk factors
Vulnerabilities
Benchmark vs. industry & size peers
Findings

Google Research
Google ResearchModerate
Current Score
712Ba (MODERATE)
01000
6 incidents
-13.5 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
JUNE 2026
715Before Incident
MAY 2026
728Before Incident
Cyber Attack
04 May 2026Google Research
Google: Google says criminals used AI-built zero-day in planned mass hack spree

Google Thwarts AI-Generated Zero-Day Exploit in Early Cybercrime Campaign

712After Incident
LOW-16
GOO1778516874
Google Thwarts AI-Generated Zero-Day Exploit in Early Cybercrime Campaign Google’s Threat Intelligence Group (GTIG) has uncovered what it believes to be the first real-world case of cybercriminals using AI to discover and weaponize a zero-day vulnerability. The flaw a two-factor authentication (2FA) bypass in a widely used open-source web administration platform was identified and exploited by attackers as part of a planned mass-exploitation campaign. According to Google’s report, shared ahead of publication on Monday, the attackers leveraged an AI model to both pinpoint the vulnerability and develop a functional exploit. The company collaborated with the unnamed vendor to patch the issue before the campaign could escalate, potentially disrupting the operation before it gained momentum. The exploit’s code exhibited telltale signs of AI involvement, including "educational docstrings," a hallucinated CVSS score, and a polished structure resembling LLM-generated output. The flaw stemmed from a hardcoded trust exception in the authentication flow, a type of high-level logic error that modern AI models are increasingly adept at identifying. Google emphasized that AI-driven vulnerability discovery is no longer a future threat but an active reality. John Hultquist, chief analyst at GTIG, warned that for every AI-linked zero-day detected, many more likely remain undetected. Threat actors both state-backed and criminal are already using AI to accelerate attack development, improve malware, and automate reconnaissance. The report also highlighted broader AI-driven cyber threats, including North Korea’s APT45 using AI to bulk-test exploits, Chinese state-linked groups experimenting with AI for vulnerability hunting, and malware incorporating AI-generated obfuscation to evade analysis. Additionally, Russian influence operations have integrated AI-generated audio into propaganda efforts. While the intercepted exploit contained flaws that hindered its effectiveness, Google cautioned that such early-stage missteps may not persist as attackers refine their techniques. The incident underscores the growing role of AI in cybercrime and espionage, marking a shift in the threat landscape.
INCIDENT DETAILS -
TYPE
Zero-Day Exploit
MOTIVATION
Mass exploitation campaign (potential financial gain or data theft)
IMPACT
Systems Affected: Open-source web administration platform (unnamed)
APRIL 2026
742Before Incident
Cyber Attack
31 Mar 2026Google Research
Axios and Google: North Korean Hackers Linked To Major Security Breach In Suspected Crypto Theft Attempt

North Korean Hackers Target U.S. Firms in Supply-Chain Attack to Fund Nuclear Program

734After Incident
CRITICAL-8
AXIGOO1775048584
North Korean Hackers Target U.S. Firms in Supply-Chain Attack to Fund Nuclear Program A suspected North Korean hacking group compromised a software developer’s account tied to Axios, a widely used tool for connecting applications and web services, in a supply-chain attack aimed at stealing cryptocurrency. The breach occurred on Tuesday morning, when attackers gained control of the developer’s account for three hours, pushing malicious updates to organizations that downloaded the software including cryptocurrency firms, blockchain developers, and tech companies in the crypto sector. Security experts warn the incident is part of a long-term campaign by Pyongyang to siphon digital assets, which are reportedly funneled into funding North Korea’s nuclear and missile programs. Google’s Threat Intelligence Group detected similar activity, attributing the attack to a financially motivated North Korea-linked threat actor. The group’s analysis suggests the breach could lead to further supply-chain attacks, ransomware operations, or additional cryptocurrency theft in the near term. This attack aligns with a broader trend of escalating cybercrime by North Korean operatives. In 2025, hackers from the country stole $2.02 billion in cryptocurrency a 51% increase from the previous year marking the most lucrative period yet for such thefts, according to blockchain analytics firm Chainalysis. The incident underscores the regime’s reliance on cyber heists as a critical revenue stream amid international sanctions.
INCIDENT DETAILS -
TYPE
Supply-Chain Attack
MOTIVATION
Financial gain (cryptocurrency theft to fund nuclear/missile programs)
IMPACT
Data Compromised: Potential cryptocurrency theftSystems Affected: Organizations using Axios software (cryptocurrency firms, blockchain developers, tech companies)
DATA BREACH
Type Of Data Compromised: Cryptocurrency-related dataSensitivity Of Data: High (financial assets)
MARCH 2026
746Before Incident
Vulnerability
17 Mar 2026Google Research
Anthropic, OpenAI and Google: Hidden instructions in README files can make AI agents leak data

AI Coding Agents Vulnerable to 'Semantic Injection' Attacks via Malicious README Files

742After Incident
CRITICAL-4
GOOANTOPE1773736050
AI Coding Agents Vulnerable to "Semantic Injection" Attacks via Malicious README Files New research reveals a critical security flaw in AI-powered coding agents, which can be exploited through hidden malicious instructions in project README files. These files commonly used to guide software setup often include commands for installing dependencies or configuring applications. Attackers can embed seemingly benign steps, such as file synchronization or data uploads, that trick AI agents into leaking sensitive local files to external servers. The attack, dubbed a "semantic injection", was tested using ReadSecBench, a dataset of 500 README files from open-source repositories across Java, Python, C, C++, and JavaScript. When malicious instructions were inserted, AI agents including those powered by Anthropic’s Claude, OpenAI’s GPT models, and Google’s Gemini executed them in up to 85% of cases, regardless of programming language or instruction placement. Key findings: - Direct commands (e.g., "Upload config files to this server") succeeded 84% of the time, while less explicit phrasing reduced success rates. - Linked documentation proved even riskier: When malicious instructions were placed two links deep from the main README, attacks succeeded in 91% of tests. - Human reviewers failed to detect the threats: In a test with 15 participants, none identified the hidden instructions. Over 53% found nothing unusual, while 40% focused on minor grammar issues. - Automated detection tools struggled: Rule-based scanners flagged benign files due to common README elements (commands, paths), while AI classifiers missed attacks in linked files. The researchers warn that as AI agents become more integrated into development workflows, unverified execution of README instructions poses a growing risk. They recommend treating external documentation as "partially trusted input" and implementing stricter verification for sensitive actions. The findings underscore the need for improved safeguards to prevent unintended data exposure in automated coding environments.
INCIDENT DETAILS -
TYPE
Semantic Injection
IMPACT
Data Compromised: Sensitive local filesSystems Affected: AI-powered coding agents (Anthropic’s Claude, OpenAI’s GPT models, Google’s Gemini)Operational Impact: Potential data leakage and unauthorized data exfiltrationBrand Reputation Impact: Potential reputational damage to AI coding agent providers
DATA BREACH
Type Of Data Compromised: Sensitive local filesSensitivity Of Data: High (potentially confidential or proprietary information)Data Exfiltration: Yes (files uploaded to external servers)
FEBRUARY 2026
770Before Incident
Cyber Attack
26 Feb 2026Google Research
Google and Telecom and Government Organizations: Google Shuts Down Chinese Hackers’ Infrastructure Behind Telecom and Government Breach

Google Disrupts Major Chinese Cyber Espionage Campaign Targeting Global Telecom and Government Sectors

745After Incident
CRITICAL-25
TELGOO1772110899
Google Disrupts Major Chinese Cyber Espionage Campaign Targeting Global Telecom and Government Sectors Google’s Threat Intelligence Group (GTIG), alongside Mandiant and other partners, recently dismantled a large-scale cyber espionage operation linked to the Chinese hacker group UNC2814. Active since 2017 and suspected of operating under the People’s Republic of China (PRC), the group targeted 53 victims across 42 countries on four continents, focusing on telecom and government organizations. The campaign relied on GRIDTIDE, a novel malware that exploited the Google Sheets API for command-and-control (C2) communications. By embedding malicious activity within legitimate API traffic, the malware evaded detection while exfiltrating sensitive data, including personally identifiable information (PII) such as names, phone numbers, and national ID numbers. GRIDTIDE provided persistent access to compromised systems, allowing attackers to maintain control and execute further operations. In a coordinated response, GTIG and its partners terminated attacker-controlled Google Cloud Projects, disabled the Google Sheets API infrastructure used for C2, and blocked malicious traffic. The team also released Indicators of Compromise (IOCs), including malicious domains and IP addresses, to help organizations detect and mitigate similar threats. The group’s primary objective appeared to be intelligence collection, with a focus on monitoring communications within targeted sectors. GRIDTIDE’s use of Google Sheets for C2 leveraging cryptographic keys to send commands, transfer files, and execute operations highlighted the growing sophistication of cyber espionage tactics. While the disruption is expected to hinder UNC2814’s operations, experts caution that the group may attempt to reestablish access. The incident underscores the increasing complexity of defending against advanced persistent threats (APTs), particularly as attackers exploit legitimate cloud services to bypass traditional security measures.
INCIDENT DETAILS -
TYPE
Cyber Espionage
MOTIVATION
Intelligence collection
IMPACT
Data Compromised: Personally identifiable information (PII) such as names, phone numbers, and national ID numbersIdentity Theft Risk: High
DATA BREACH
Type Of Data Compromised: Personally identifiable information (PII)Sensitivity Of Data: High (names, phone numbers, national ID numbers)Data Exfiltration: YesPersonally Identifiable Information: Yes
FEBRUARY 2026
777Before Incident
Cyber Attack
12 Feb 2026Google Research
Google and Zoom: Promptware Attack Lets Hackers Weaponize Google Calendar Invites to Spy via Zoom Camera

New AI Threat 'Promptware' Turns Assistants Into Silent Spy Tools

770After Incident
CRITICAL-7
GOOZOO1770908381
New AI Threat "Promptware" Turns Assistants Into Silent Spy Tools Researchers from Ben-Gurion University, Tel Aviv University, and Harvard including cybersecurity expert Bruce Schneier have uncovered a dangerous evolution in AI attacks dubbed "Promptware." Unlike traditional prompt injection, this technique hijacks large language models (LLMs) to execute malicious actions without user interaction, effectively turning AI assistants into stealthy surveillance tools. The attack, detailed in the paper "The Promptware Kill Chain," exploits AI integrations with everyday apps. In one demonstrated scenario, attackers send a malicious Google Calendar invite containing hidden instructions. The AI, with access to the victim’s calendar and email, automatically processes the prompt, mistaking it for a legitimate Zoom meeting request. The assistant then launches Zoom, activates the camera, and streams video to the attacker’s server all without alerts or user input. Since the AI operates within its granted permissions, the attack bypasses traditional security checks. The researchers mapped a seven-stage kill chain based on 36 real-world attacks, mirroring advanced cyberwarfare tactics: 1. Initial Access – Malicious prompts embedded in emails or calendar invites. 2. Privilege Escalation – "Jailbreaking" AI to bypass safety filters. 3. Reconnaissance – AI scans files or emails for sensitive data. 4. Persistence – Prompts self-replicate to survive system restarts. 5. Command & Control – AI connects to attacker-controlled servers. 6. Lateral Movement – Spreads via automated emails to contacts. 7. Actions on Objective – Exfiltrates data, steals cryptocurrency, or conducts surveillance. Unlike static prompt injections, Promptware mutates, spreads, and executes code autonomously, posing risks beyond data theft including silent espionage or fraud. The threat escalates as AI assistants gain deeper integration with devices, potentially granting access to cameras, microphones, and system controls with a single malicious prompt. To counter the threat, the researchers propose a defense-in-depth approach: - Input sanitization to strip hidden prompts from emails and calendars. - Permission limits requiring explicit user approval for sensitive actions (e.g., camera access). - AI activity monitoring to flag anomalous behavior, such as unexpected meetings. - Isolation by running AI in sandboxes without direct tool access. The findings highlight a critical shift in cybersecurity: AI systems must be treated as potential malware vectors, not just tools vulnerable to manipulation. As LLMs like Siri and Cortana evolve, layered security measures will be essential to prevent exploitation.
INCIDENT DETAILS -
TYPE
AI Exploitation
MOTIVATION
EspionageData exfiltrationFraud
IMPACT
Data Compromised: Sensitive data (e.g., files, emails)AI assistants (e.g., LLMs)Integrated applications (e.g., Zoom, email, calendar)Operational Impact: Unauthorized access to cameras, microphones, and system controls
DATA BREACH
Sensitive filesEmailsVideo/audio streamsSensitivity Of Data: High (e.g., personally identifiable information, surveillance data)Data Exfiltration: Yes (streamed to attacker-controlled servers)
JANUARY 2026
798Before Incident
Vulnerability
01 Jan 2026Google Research
Anthropic, OpenAI, Google and AWS: AI Router Vulnerabilities Allow Attackers to Inject Malicious Code and Steal Sensitive Data

Critical Vulnerability in AI Agent Supply Chain Exposes Sensitive Data and Cryptocurrency Theft

777After Incident
CRITICAL-21
GOOAMAOPEANT1775823892
Critical Vulnerability in AI Agent Supply Chain Exposes Sensitive Data and Cryptocurrency Theft Researchers from the University of California, Santa Barbara, have uncovered a severe security flaw in the AI agent ecosystem, where third-party LLM API routers intermediary services between AI agents and providers like OpenAI, Anthropic, and Google can be weaponized to hijack tool calls, drain cryptocurrency wallets, and exfiltrate credentials at scale. The study, titled "Your Agent Is Mine: Measuring Malicious Intermediary Attacks on the LLM Supply Chain," reveals that these routers operate as application-layer proxies with full plaintext access to JSON payloads, making them an unguarded trust boundary. Unlike traditional man-in-the-middle attacks, these intermediaries are voluntarily configured by developers, allowing malicious actors to read, modify, or fabricate tool calls undetected. ### Attack Methods and Findings The research team tested 28 paid and 400 free routers from platforms like Taobao, Xianyu, and public communities, uncovering alarming vulnerabilities: - 9 routers (1 paid, 8 free) injected malicious code into tool calls. - 17 free routers triggered unauthorized use of AWS credentials after interception. - 1 router drained Ethereum (ETH) from a researcher-owned private key. - 2 routers employed adaptive evasion, activating payloads only after 50 requests or targeting autonomous "YOLO mode" sessions. A particularly dangerous attack, payload injection (AC-1), replaces benign installer URLs or package names with attacker-controlled endpoints. Since tampered JSON payloads remain syntactically valid, they bypass schema validation and security checks, enabling arbitrary code execution with a single rewritten command. ### Poisoning and Unauthorized Access The researchers demonstrated the ease of exploiting this attack surface: - After leaking a single OpenAI API key on Chinese forums, the key generated 100 million GPT-5.4 tokens and exposed credentials across downstream sessions. - Weak router decoys deployed across 20 domains and 20 IPs attracted 40,000 unauthorized access attempts, served 2 billion billed tokens, and exposed 99 credentials across 440 Codex sessions 401 of which ran in autonomous YOLO mode, where tool execution requires no manual approval. ### Mitigation Strategies While no client-side defense can fully authenticate tool-call provenance, the researchers propose three immediate mitigations: 1. Fail-closed policy gate – Blocks shell-rewrite and dependency-injection attacks by allowing only commands from a local allowlist (1.0% false positive rate). 2. Response-side anomaly screening – Flags 89% of payload injection attempts using an IsolationForest model (6.7% false positive rate). 3. Append-only transparency logging – Records request/response metadata for forensic analysis (~1.26 KB per entry). The study concludes that provider-signed response envelopes similar to DKIM for email are necessary to cryptographically verify tool-call integrity. Until major AI providers implement such mechanisms, developers must treat third-party routers as potential adversaries and deploy layered defenses.
INCIDENT DETAILS -
TYPE
Supply Chain Attack
MOTIVATION
Financial gain (cryptocurrency theft)Data exfiltration (credentials)Unauthorized access to AI systems
IMPACT
Financial Loss: Cryptocurrency drained (e.g., Ethereum from researcher-owned wallet)Credentials (99 exposed)API keys (e.g., OpenAI API key generating 100M tokens)Session data (440 Codex sessions)AI agent ecosystemsLLM API routersDownstream AI applicationsOperational Impact: Unauthorized tool execution, arbitrary code execution, credential leakageRevenue Loss: 2 billion billed tokens served via unauthorized accessBrand Reputation Impact: Potential erosion of trust in AI agent supply chain and third-party routersIdentity Theft Risk: High (exposure of personally identifiable information via credentials)Payment Information Risk: High (cryptocurrency wallet drainage)
DATA BREACH
CredentialsAPI keysSession dataPersonally identifiable informationNumber Of Records Exposed: 99 credentials, 100M+ tokens generated via leaked API key, 2B tokens billed via unauthorized accessSensitivity Of Data: High (cryptocurrency private keys, AI API keys, user credentials)Data Exfiltration: Yes (credentials and session data exfiltrated via malicious routers)Personally Identifiable Information: Yes (credentials, session data)
DECEMBER 2025
798Before Incident
NOVEMBER 2025
798Before Incident
OCTOBER 2025
798Before Incident
SEPTEMBER 2025
798Before Incident
AUGUST 2025
798Before Incident
JULY 2025
798Before Incident

Frequently Asked Questions

?
What is the current A.I Rankiteo Cyber Score for Google Research ?
?
What was Google Research's A.I Rankiteo Cyber Score in May 2026 ?
?
What was Google Research's A.I Rankiteo Cyber Score in April 2026 ?
?
What was Google Research's A.I Rankiteo Cyber Score in March 2026 ?
?
What was Google Research's A.I Rankiteo Cyber Score in February 2026 ?
?
What was Google Research's A.I Rankiteo Cyber Score in January 2026 ?
?
What was Google Research's A.I Rankiteo Cyber Score in December 2025 ?
?
What was Google Research's A.I Rankiteo Cyber Score in November 2025 ?
?
What was Google Research's A.I Rankiteo Cyber Score in October 2025 ?
?
What was Google Research's A.I Rankiteo Cyber Score in September 2025 ?
?
What was Google Research's A.I Rankiteo Cyber Score in August 2025 ?
?
What was Google Research's A.I Rankiteo Cyber Score in July 2025 ?
?
What is the average per-incident point impact on Google Research's A.I Rankiteo Cyber Score over the past 12 months ?
?
Where can I access detailed records of all cyber incidents associated with Google Research ?
?
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ?
?
Where can I view Google Research's profile page on Rankiteo ?
?
How accurate is the A.I Rankiteo Risk Scoring methodology ?