EN ES PT
Back to Stats

Visual Capture

Screenshot of docs.google.com

Detection Info

https://docs.google.com/document/d/1dtAbpjRNnd6dpERGsE5m2hzMgrHaDn2eRU-ylXcaWMg/edit?tab=t.0
Detected Brand
JCB
Country
Japan (implied by the .co.jp TLD)
Confidence
100%
HTTP Status
200
Report ID
a88339d4-558…
Analyzed
2026-01-30 04:33

Content Hashes (HTML Similarity)

Used to detect similar phishing pages based on HTML content

Algorithm Hash Value
CONTENT TLSH
T12CE3BD32C0423033A1AB56D5F860677926D3C22DDF0B08452BBCDB963FEBD967592A1D
CONTENT ssdeep
3072:egA76cUOugiUhoSWeBYVplVX/cn3x/hSCVuDdi5NvHao7LVq3u/19/JSA4LGZPI8:JA76cUOugiUhoSWeBYVplVX/cn3x/hSg

Visual Hashes (Screenshot Similarity)

Used to detect visually similar phishing pages based on screenshots

Algorithm Hash Value
VISUAL pHash
911155555d7d7d28
VISUAL aHash
003c3cbc3c3c3c3c
VISUAL dHash
b0d8f06060606060
VISUAL wHash
003d7cfc3c3c3c3c
VISUAL colorHash
07200008180
VISUAL cropResistant
b0d8f06060606060

Code Analysis

Risk Score 97/100
Threat Level ALTO
⚠️ Phishing Confirmed
🎣 Credential Harvester 🎣 OTP Stealer 🎣 Card Stealer 🎣 Banking 🎣 Personal Info

🔬 Threat Analysis Report

• Threat: Impersonation/Phishing
• Target: JCB (potential target of the phishing attempt)
• Method: Domain spoofing, social engineering
• Exfil: Potentially the target domain will collect credentials.
• Indicators: Domain mismatch, suspicious content, text in Japanese language.
• Risk: High

🔒 Obfuscation Detected

  • atob
  • eval
  • fromCharCode
  • unescape
  • document.write
  • hex_escape
  • unicode_escape
  • base64_strings

📡 API Calls Detected

  • POST
  • a
  • i
  • h5
  • h6
  • p
  • h4
  • u
  • GoogleDocs
  • kbd
  • h1
  • blockquote

📊 Risk Score Breakdown

Total Risk Score
90/100

Contributing Factors

Domain Mismatch
The domain my.jcb.co.jp does not align with the perceived Google Docs branding.
Suspicious Content
The prompt to access another domain is unusual and suspicious within Google Docs context. The content is written in Japanese and the file is named 'MyJcb' which is a clue.
Obfuscation
Javascript Obfuscation detected in the source code.

🔬 Comprehensive Threat Analysis

Threat Type
Banking Credential Harvester
Target
JCB users (Japan (implied by the .co.jp TLD))
Attack Method
Brand impersonation + credential harvesting forms + obfuscated JavaScript
Exfiltration Channel
Form submission (backend endpoint not detected - likely JavaScript-based)
Risk Assessment
CRITICAL - Automated credential harvesting with Form submission (backend endpoint not detected - likely JavaScript-based)

⚠️ Indicators of Compromise

  • Kit types: Credential Harvester, OTP Stealer, Card Stealer, Banking, Personal Info
  • 10557 obfuscation techniques

🏢 Brand Impersonation Analysis

Impersonated Brand
Google Docs and JCB (indirectly)
Official Website
docs.google.com and jcb.co.jp
Fake Service
Document access (Google Docs) and JCB (indirectly)

⚔️ Attack Methodology

Primary Method: Credential Harvesting

The attackers are likely attempting to steal the user's credentials by leading them to a fake login page on the my.jcb.co.jp domain. They probably use a phishing technique.

Secondary Method: Social Engineering

The attacker uses the document title to trick the user.

🌐 Infrastructure Indicators of Compromise

Domain Information

Domain
docs.google.com
Registered
None
Registrar
None
Status
Active

🤖 AI-Extracted Threat Intelligence

😰
"I Never Thought It Would Happen to Me"
That's what 2.3 million victims say every year. Don't wait to become a statistic.