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

Incident Score: Analysis & Impact (UNIGOO1776879280)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-12
Company Score Before Incident466 / 1000
Company Score After Incident454 / 1000
INCIDENT NUMBERUNIGOO1776879280
Type of Cyber IncidentCyber Attack
ATTACK VECTORMalicious Google Ads, Fake DeFi/Wallet Websites, Browser Extensions, Man-in-the-Middle Proxy
DATA EXPOSEDSeed phrases, Wallet credentials, Blockchain...
INCIDENT DATE28/02/2026
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Google's Cyber Attack and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Google Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Google breach identified under incident ID UNIGOO1776879280.

The analysis begins with a detailed overview of Google's information like the linkedin page: https://www.linkedin.com/company/google, the number of followers: 40050213, the industry type: Software Development and the number of employees: 327709 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 466 and after the incident was 454 with a difference of -12 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Google and their customers.

Google Ads recently reported "Malicious Google Ads Fuel Surge in Crypto Wallet Drain Attacks", a noteworthy cybersecurity incident.

Cybercriminals are increasingly exploiting Google Ads to steal cryptocurrency, targeting users searching for legitimate DeFi apps and wallet services.

The disruption is felt across the environment, affecting User wallets, DeFi platforms and Browser extensions, and exposing Seed phrases, Wallet credentials and Blockchain transaction data, plus an estimated financial loss of Cryptocurrency stolen (amount unspecified).

In response, moved swiftly to contain the threat with measures like Blocking malicious ad URLs and Suspension of advertiser accounts, and began remediation that includes Takedown of malicious infrastructure and Monitoring for new campaigns.

The case underscores how Ongoing, teams are taking away lessons such as Challenges in fully containing malicious ad campaigns due to rapid attacker adaptation and abuse of high-reputation domains. Need for improved detection of cloaking/fingerprinting techniques and collaboration between ad platforms and security firms, and recommending next steps like Enhanced vetting of advertisers for high-risk categories (e.g., crypto), Real-time monitoring for cloaking/fingerprinting in ads and Collaboration with security firms to track and block malicious infrastructure, with advisories going out to stakeholders covering Users advised to verify DeFi/wallet service URLs and avoid clicking on ads for such services.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Phishing: Spearphishing Link (T1566.002) with high confidence (90%), supported by evidence indicating malicious Google Ads targeting users searching for legitimate DeFi apps and Drive-by Compromise (T1189) with moderate to high confidence (80%), supported by evidence indicating fake versions of trusted platforms (e.g., Uniswap, Ledger) used to drain wallets. Under the Execution tactic, the analysis identified User Execution: Malicious Link (T1204.001) with high confidence (90%), supported by evidence indicating users tricked into clicking malicious ads leading to wallet drainers and User Execution: Malicious File (T1204.002) with moderate to high confidence (70%), supported by evidence indicating malicious browser extensions distributed via Chrome Web Store. Under the Defense Evasion tactic, the analysis identified Masquerading: Match Legitimate Name or Location (T1036.005) with high confidence (90%), supported by evidence indicating spoofed front ends mimicking legitimate sites (e.g., Uniswap, Ledger), Obfuscated Files or Information (T1027) with moderate to high confidence (80%), supported by evidence indicating obfuscated payloads stored on irys.xyz using runtime code construction, Hide Artifacts: Hidden Files and Directories (T1564.001) with moderate to high confidence (70%), supported by evidence indicating malicious payloads hosted in secondary iframes or off-platform infrastructure, Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating abuse of high-reputation Google domains (sites.google.com, docs.google.com), and Detect Browser Fingerprinting (T1642) with moderate to high confidence (80%), supported by evidence indicating fingerprinting used to serve malicious content only to targeted victims. Under the Credential Access tactic, the analysis identified Adversary-in-the-Middle: ARP Poisoning (T1557.002) with moderate to high confidence (70%), supported by evidence indicating man-in-the-middle proxy rerouting API/RPC traffic through attacker domains and Credentials from Password Stores: Credentials from Web Browsers (T1555.003) with moderate to high confidence (80%), supported by evidence indicating seed phrases and wallet credentials harvested via fake wallet sites. Under the Collection tactic, the analysis identified Data from Information Repositories: Sharepoint (T1213.002) with moderate confidence (60%), supported by evidence indicating abuse of docs.google.com to host convincing ads and Command and Scripting Interpreter: JavaScript (T1059.007) with moderate to high confidence (70%), supported by evidence indicating malicious blockchain transactions signed in-browser via drainer tools. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating wallet draining and seed phrase harvesting via malicious payloads. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (80%), supported by evidence indicating cryptocurrency stolen via wallet drainers (Inferno Drainer, Vanilla Drainer). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Phishing: Spearphishing Link (90%)
Drive-by Compromise (80%)
Execution
User Execution: Malicious Link (90%)
User Execution: Malicious File (70%)
Defense Evasion
Masquerading: Match Legitimate Name or Location (90%)
Obfuscated Files or Information (80%)
Hide Artifacts: Hidden Files and Directories (70%)
Valid Accounts: Cloud Accounts (80%)
Detect Browser Fingerprinting (80%)
Credential Access
Adversary-in-the-Middle: ARP Poisoning (70%)
Credentials from Password Stores: Credentials from Web Browsers (80%)
Collection
Data from Information Repositories: Sharepoint (60%)
Command and Scripting Interpreter: JavaScript (70%)
Exfiltration
Exfiltration Over C2 Channel (90%)
Impact
Resource Hijacking (80%)

Sources & References