EN ES PT
Back to Stats

Visual Capture

Screenshot of bet83088.com

Detection Info

https://bet83088.com/about/contact
Detected Brand
bet365
Country
International
Confidence
100%
HTTP Status
200
Report ID
5b59ba51-137โ€ฆ
Analyzed
2026-02-06 12:03
Final URL (after redirects)
https://bet83088.com/about/contact#

Content Hashes (HTML Similarity)

Used to detect similar phishing pages based on HTML content

Algorithm Hash Value
CONTENT TLSH
T108D22EB09156AA3B02F392E1AB752B6FB3D5E2C8D94307052AFCC75D4FCEE94E921051
CONTENT ssdeep
384:cL3Ubc+VW8Cvq87CygUyD084mR8m9Q8lzK:cLmc+VDCC1WQ8yVK

Visual Hashes (Screenshot Similarity)

Used to detect visually similar phishing pages based on screenshots

Algorithm Hash Value
VISUAL pHash
868e93f1f1e1a88e
VISUAL aHash
ff14102038002020
VISUAL dHash
4c6d655270444840
VISUAL wHash
ff0410bb3c3c2c2c
VISUAL colorHash
0f000000e00
VISUAL cropResistant
4c6d655270444840

Code Analysis

Risk Score 100/100
Threat Level ALTO
โš ๏ธ Phishing Confirmed
๐ŸŽฃ Credential Harvester ๐ŸŽฃ OTP Stealer ๐ŸŽฃ Card Stealer ๐ŸŽฃ Banking ๐ŸŽฃ Personal Info

๐Ÿ”ฌ Threat Analysis Report

โ€ข Threat: Impersonation Phishing
โ€ข Target: bet365 users
โ€ข Method: Domain spoofing with visual mimicry
โ€ข Exfil: /login_action
โ€ข Indicators: Domain mismatch, obfuscation, form actions
โ€ข Risk: High

๐Ÿ” Credential Harvesting Forms

๐Ÿ”’ Obfuscation Detected

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

๐ŸŽฏ Kit Endpoints

  • //3f38sfb.qdhyxt.com/plus/css/custom/login_modal_custom.css?ver=1726650059?v=1770382074
  • https://3f38sfb.qdhyxt.com/plus/plugin/js/swiper.min.js?ver=1598106537
  • //3f38sfb.qdhyxt.com/images_plus/footer/footer-logo.png?ver=1600719130
  • //3f38sfb.qdhyxt.com/images_plus/main/logo.gif?ver=1612839866
  • https://bet83088.com/plus/js/unite/crypto-js.min.js
  • https://3f38sfb.qdhyxt.com/plus/js/unite/encforms.js?ver=1761119296
  • /logout
  • /login_action
  • https://3f38sfb.qdhyxt.com/plus/js/custom/checkinput.js?ver=1598008226
  • https://npmcdn.com/[email protected]/LICENSE.txt
  • http://kjur.github.io/jsrsasign/license/
  • https://ssl.captcha.qq.com/TCaptcha.js
  • http://www.idangero.us/swiper/
  • http://www-cs-students.stanford.edu/~tjw/jsbn/
  • https://3f38sfb.qdhyxt.com/assets/js/caller.js?ver=1675418258
  • //3f38sfb.qdhyxt.com/plus/js/custom/login.js?ver=1597629260
  • //3f38sfb.qdhyxt.com/plus/css/unite/login_unite.css?ver=1614680239
  • #normalLogin
  • https://3f38sfb.qdhyxt.com/plus/js/custom/login.js?ver=1597629260
  • https://3f38sfb.qdhyxt.com/plus/plugin/js/sweetalert.min.js?ver=1598106537
  • //3f38sfb.qdhyxt.com/plus/js/custom/login_custom.js?ver=1598008226
  • //3f38sfb.qdhyxt.com/plus/css/unite/login_modal_unite.css?ver=1738950076?v=1770382074
  • https://3f38sfb.qdhyxt.com/plus/js/custom/main.js?ver=1598008226
  • https://3f38sfb.qdhyxt.com/plus/js/unite/share_unite.js?ver=1749181409
  • //3f38sfb.qdhyxt.com/plus/css/custom/login_custom.css?ver=1663905027
  • https://bet83088.com/js/www/decrypt.js
  • https://3f38sfb.qdhyxt.com/plus/js/unite/jsencrypt.min.js?ver=1598106537

๐Ÿ“ก API Calls Detected

  • /loadGame/
  • https://5sx5x5y.bipnzhh8.com/03694358abf04e8jkfle-keli6c4e59a3f8458672b518938744adfbd2b99a2ede4903545d86cda66e48a54429
  • /mbuhx0as4kui
  • /agent/login
  • /forgot
  • /prizedraw/default
  • POST

๐Ÿ“ค Form Action Targets

  • /login_action

๐Ÿ“Š Risk Score Breakdown

Total Risk Score
90/100

Contributing Factors

Domain Mismatch
The domain does not match the legitimate bet365 domain.
Obfuscation Detected
Obfuscated Javascript code is a common tactic of malicious actors to hide their code.
Forms Collecting Sensitive Data
The site asks for login credentials.

๐Ÿ”ฌ Comprehensive Threat Analysis

Threat Type
Banking Credential Harvester
Target
bet365 users (International)
Attack Method
Brand impersonation + credential harvesting forms + obfuscated JavaScript
Exfiltration Channel
HTTP POST to backend
Risk Assessment
CRITICAL - Automated credential harvesting with HTTP POST to backend

โš ๏ธ Indicators of Compromise

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

๐Ÿข Brand Impersonation Analysis

Impersonated Brand
bet365
Official Website
https://www.bet365.com
Fake Service
bet365 login

โš”๏ธ Attack Methodology

Primary Method: Credential Harvesting

The attacker is attempting to steal user credentials by creating a fake login page that closely resembles the legitimate bet365 website. Users entering their username and password will have their credentials stolen.

๐ŸŒ Infrastructure Indicators of Compromise

๐Ÿฆ  Malicious Files

Main File
encforms.js (handles encrypted form submission) and checkinput.js (contains credential validation logic)
File Size

Functions: checkPassword(), checkConfirmPassword(), getcode(), $('#btnSubmit').click(), $.ajax() and $.post() calls in form submission handlers, playgame_modal() (likely a decoy or secondary payload delivery mechanism)

๐Ÿ“Š Attack Flow Diagram

1. Step 1: User lands on phishing page and fills out registration/login form (fields: userid, password1, confirmpassword1, realname, tel, email, question, answer)
2. Step 2: Form validation functions (e.g., checkPassword, checkEmail) execute client-side checks to mimic legitimacy
3. Step 3: On submission, $('#btnSubmit').click() triggers AJAX POST to /getcode with affiliate code or other data
4. Step 4: For login forms, encrypted credentials are sent via $.post('/login_action') using JSEncrypt to obfuscate payloads
5. Step 5: Server processes data (e.g., stores credentials, triggers secondary actions like fake 'success' alerts or redirects)
6. Step 6: Decoy functionality (e.g., playgame_modal) may distract users or deliver additional payloads

๐Ÿ”ฌ JavaScript Deep Analysis

Total Code Size
265.1ย KB

๐Ÿ”— API Endpoints Detected

Other
5

๐Ÿ” Obfuscation Detected

  • : Light
  • : None
  • : None
  • : Moderate
  • : Light
  • : Light
  • : None
  • : None
  • : Moderate
  • : None
  • : None

๐Ÿค– AI-Extracted Threat Intelligence

๐Ÿ“Š Attack Flow

1. Step 1: User lands on phishing page and fills out registration/login form (fields: userid, password1, confirmpassword1, realname, tel, email, question, answer)
2. Step 2: Form validation functions (e.g., checkPassword, checkEmail) execute client-side checks to mimic legitimacy
3. Step 3: On submission, $('#btnSubmit').click() triggers AJAX POST to /getcode with affiliate code or other data
4. Step 4: For login forms, encrypted credentials are sent via $.post('/login_action') using JSEncrypt to obfuscate payloads
5. Step 5: Server processes data (e.g., stores credentials, triggers secondary actions like fake 'success' alerts or redirects)
6. Step 6: Decoy functionality (e.g., playgame_modal) may distract users or deliver additional payloads

๐ŸŽฏ Malicious Files Identified

Main Drainer
encforms.js (handles encrypted form submission) and checkinput.js (contains credential validation logic)
File Size
~50KB (aggregated from multiple JS files)
Malicious Functions
  • checkPassword()
  • checkConfirmPassword()
  • getcode()
  • $('#btnSubmit').click()
  • $.ajax() and $.post() calls in form submission handlers
  • playgame_modal() (likely a decoy or secondary payload delivery mechanism)
๐Ÿ˜ฐ
"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.